more fixes

Author: stayseesong

src/connections/sources/catalog/libraries/website/javascript/persistence.md

@@ -9,9 +9,9 @@ This page explains what data Analytics.js stores on the client and how to overri
 
 <!-- Note: 1st 2 paragraphs copied from identity.md -->
 
-To ensure high fidelity, first-party customer data, Segment writes the user's IDs to the user's localStorage, and uses that as the Segment ID on the cookie whenever possible. LocalStorage is meant for storing this type of first-party customer information.
+To ensure high fidelity, first-party customer data, Segment writes the user's IDs to the user's local storage, and uses that as the Segment ID on the cookie whenever possible. Local Storage is meant for storing this type of first-party customer information.
 
-If a user returns to your site after the cookie expires, Analytics.js looks for an old ID in the user's `localStorage`, and if one is found, sets it as the user's ID again in the new cookie. If a user clears their cookies _and_ `localstorage`, all of the IDs are removed, and the user gets a completely new [anonymousID](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/identity/#anonymous-ids) when they next visit the page.
+If a user returns to your site after the cookie expires, Analytics.js looks for an old ID in the user's `localStorage`, and if one is found, sets it as the user's ID again in the new cookie. If a user clears their cookies _and_ `localStorage`, all of the IDs are removed, and the user gets a completely new [`anonymousID`](/docs/connections/sources/catalog/libraries/website/javascript/identity/#anonymous-ids) when they next visit the page.
 
 ### Cookie Settings
 
@@ -51,7 +51,7 @@ The user object has the following fields and default values:
 | `persist` | This toggles storing user information locally. | `true` |
 | `cookie.key` | Name of the cookie used to store the user ID. | `ajs_user_id` |
 | `cookie.oldKey` | Name of a cookie previously used to store the user ID. Will be read if `cookie.key` can't be found. | `ajs_user` |
-| `localStorage.key` | Name of the key used to store user traits in LocalStorage. | `ajs_user_traits` |
+| `localStorage.key` | Name of the key used to store user traits in localStorage. | `ajs_user_traits` |
 
 Example:
 ```js
@@ -70,15 +70,15 @@ analytics.load('writeKey', {
 
 ### Group Settings
 
-Analytics.js automatically persists the user's group ID and group properties locally. You can override how and where the group ID and properties are stored when loading analytics.js by passing in a `group` object to the load method.
+Analytics.js automatically persists the user's group ID and group properties locally. You can override how and where the group ID and properties are stored when loading Analytics.js by passing in a `group` object to the load method.
 
 The group object has the following fields and default values:
 
 | Field | Description | Default value |
 | ----- | ----------- | ------------- |
 | `persist` | Toggles storing group information locally. | `true` |
 | `cookie.key` | Name of the cookie used to store the group id. | `ajs_group_id` |
-| `localStorage.key` | Name of the key used to store user traits in LocalStorage. | `ajs_group_properties` |
+| `localStorage.key` | Name of the key used to store user traits in localStorage. | `ajs_group_properties` |
 
 Example:
 ```js
@@ -112,12 +112,12 @@ analytics.load('writeKey', { disableClientPersistence: true })
 
 ### Identity
 
-When `disableClientPersistence` is set to `true`, Analytics.js will not be able to automatically keep track of a user's identity when navigating to different pages. This can cause increased MTU usage if the anonymous usage cannot be associated with a `userId`.
+When `disableClientPersistence` is set to `true`, Analytics.js won't be able to automatically keep track of a user's identity when navigating to different pages. This can cause increased MTU usage if the anonymous usage can't be associated with a `userId`.
 
-You can still manually track identity by calling `analytics.identify()` with the known identity on each page load, or pass in identity information to each page using the [querystring API](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/querystring/).
+You can still manually track identity by calling `analytics.identify()` with the known identity on each page load, or you can pass in identity information to each page using the [querystring API](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/querystring/).
 
 ### Event Retries
 
-Analytics.js tries to detect when a page is about to be closed and saves pending events to `localStorage`. When the user navigates to another page within the same domain, analytics.js will attempt to send any events it finds in localStorage.
+Analytics.js tries to detect when a page is about to be closed and saves pending events to `localStorage`. When the user navigates to another page within the same domain, Analytics.js attempts to send any events it finds in localStorage.
 
-When `disableClientPersistence` is set to `true`, Analytics.js will not store any pending events into `localStorage`.
+When `disableClientPersistence` is set to `true`, Analytics.js won't store any pending events into `localStorage`.