Apply suggestions from code review

stayseesong · pwseg · web-flow · commit 3f4c66108694 · 2021-11-17T09:08:55.000-08:00
Co-authored-by: pwseg &lt;86626706+pwseg@users.noreply.github.com&gt;
diff --git a/src/connections/storage/data-lakes/sync-history.md b/src/connections/storage/data-lakes/sync-history.md
@@ -23,7 +23,7 @@ To access the Sync History page from the Segment app, open the **My Destinations
 ## Health
 The health tab provides an overview of the rows that synced to your data lake both today and each day for the last 30 days. 
 
-The bar chart, 'Daily Synced Rows,' shows an overview of the rows synced for each of the last 30 days. Hovering over a date shows the number of rows that were synced for that day. Selecting a date from the bar chart opens the Daily Row Volume table, which provides a breakdown of which collections synced, how many rows from each collection synced, and the percentage of all synced rows from each collection .
+The bar chart, 'Daily Synced Rows,' shows an overview of the rows synced for each of the last 30 days. Hovering over a date shows the number of rows that were synced for that day. Selecting a date from the bar chart opens the Daily Row Volume table, which provides a breakdown of which collections synced, how many rows from each collection synced, and the percentage of all synced rows from each collection.
 
 The Daily Row Volume table contains the following information:
 * **Collections:** The name of each collection of properties synced to the data lake
diff --git a/src/getting-started/02-simple-install.md b/src/getting-started/02-simple-install.md
@@ -38,7 +38,7 @@ To create a Segment source:
 
 ## Find your write key
 
-The write key is the unique identifier for a source that tells Segment which source data comes from, to which workspace the data belongs to, and which destinations should receive the data.
+The write key is the unique identifier for a source that tells Segment which source data comes from, to which workspace the data belongs, and which destinations should receive the data.
 
 To find your write key:
 1. Go to **Connections > Sources** and select your source.
@@ -51,7 +51,7 @@ Any time you change a library's settings in the Segment App, the write key regen
 ![](/docs/connections/images/find_writekey.png)
 
 > info ""
-> [Cloud-sources](/docs/connections/sources/about-cloud-sources/) do not have write keys, as they use a token or key from your account with that service. Cloud-sources have other considerations, and aren't part of this tutorial.
+> [Cloud-sources](/docs/connections/sources/about-cloud-sources/) do not have write keys, as they use a token or key from your account with that service. Cloud-sources have other considerations and aren't part of this tutorial.
 
 ## Installing Segment
 
@@ -67,7 +67,7 @@ Click a tab below to see the tutorial content for the specific library you chose
 
 ### Step 1: Copy the Snippet
 <br>
-Paste the snippet from the Javascript Source overview page into the `<head>` tag of your site.
+Paste the snippet from the JavaScript Source overview page into the `<head>` tag of your site.
 <br><br>
 That snippet loads Analytics.js onto the page _asynchronously_, so it won't affect your page load speed. Once the snippet runs on your site, you can turn on destinations from the destinations page in your workspace and data starts loading on your site automatically.
 <br><br>
@@ -210,15 +210,15 @@ This call identifies Michael by his unique User ID (`f4ca124298`, which is the o
 <br>
 The `track` method is how you tell Segment about the actions your users are performing in your app. Every action triggers what we call an "event", which can also have associated properties. You can read more about `track` in the [track method reference](/docs/connections/sources/catalog/libraries/mobile/ios#track).
 
-The Segment iOS SDK can automatically track a few important common events, such as **Application Installed**, **Application Updated** and **Application Opened**. You can enable this option during initialization by adding the following lines:
+The Segment iOS SDK can automatically track a few important common events, such as **Application Installed**, **Application Updated**, and **Application Opened**. You can enable this option during initialization by adding the following lines:
 
 ```objc
 SEGAnalyticsConfiguration *configuration = [SEGAnalyticsConfiguration configurationWithWriteKey:@"YOUR_WRITE_KEY"];
 configuration.trackApplicationLifecycleEvents = YES;
 [SEGAnalytics setupWithConfiguration:configuration];
 ```
 <br>
-You should also track events that indicate success in your mobile app, like **Signed Up**, **Item Purchased** or **Article Bookmarked**. Segment recommends that you track a few important events as you can always add more later.
+You should also track events that indicate success in your mobile app, like **Signed Up**, **Item Purchased**, or **Article Bookmarked**. Segment recommends that you track a few important events as you can always add more later.
 <br><br>
 Here's what a `track` call might look like when a user signs up:
 
@@ -277,7 +277,7 @@ class_alias('Segment', 'Analytics');
 Segment::init("YOUR_WRITE_KEY");
 ```
 <br>
-4) Replace `YOUR_WRITE_KEY` with the actual write key, which you can find in Segment under your project settings. Otherwise all that data goes straight to `/dev/null`.
+4) Replace `YOUR_WRITE_KEY` with the actual write key, which you can find in Segment under your project settings. Otherwise, all that data goes straight to `/dev/null`.
 <br><br>
 You only need to call `init` once when your php file is requested. All of your files then have access to the same `Analytics` client.
 
