Bump target API to 33. https://redmine.stoutner.com/issues/902

[PrivacyBrowserAndroid.git] / app / src / main / assets / tr / guide_local_storage.html

diff --git a/app/src/main/assets/tr/guide_local_storage.html b/app/src/main/assets/tr/guide_local_storage.html
index 5d41db2d6af848c02c1d7cb91eb705a79e627ebf..1f643df28940c1c2c223b5acbab2c1ecbb476210 100644 (file)
--- a/app/src/main/assets/tr/guide_local_storage.html
+++ b/app/src/main/assets/tr/guide_local_storage.html
@@ -44,7 +44,7 @@
         <p>Almost all websites with logins require cookies to be enabled for a user to log in.
             That is how they make sure it is still you as you move from page to page on the site, and is, in my opinion, the only legitimate use for cookies.</p>
 
-        <p>Android's System WebView treats cookies as an app level setting, meaning that cookies are either on or off for all tabs in Privacy Browser.
+        <p>Android's System WebView treats cookies as an app-level setting, meaning that cookies are either on or off for all tabs in Privacy Browser.
             The result is that the cookies setting for whatever tab is currently displayed controls the cookies setting for all the background tabs as well.
             If you have a tab in that background that has cookies enabled so that you can be logged into a website, and switch to a tab that doesn't have cookies enabled, it disabled cookies for all the tabs.
             If the background tab makes a request, for example, to see if there is updated information, that request will be sent without cookies, which will cause the website to log you out.