DOC-241

Author: stayseesong

src/_data/sidenav/main.yml

@@ -24,21 +24,21 @@ sections:
   - path: /guides
     title: An introduction to Segment
   - path: /guides/intro-impl
-    title: Segment developer overview
+    title: Segment for developers
   - path: /guides/intro-user
-    title: Segment data user overview
+    title: Segment for data users
   - path: /guides/intro-admin
-    title: Segment workspace admin overview
+    title: Segment for workspace admins
   - path: /guides/filtering-data
     title: Filtering your Segment data
   - path: /guides/duplicate-data
-    title: How does Segment handle duplicate data?
+    title: Handling duplicate data
   - path: /guides/ignore-bots
-    title: How can I ignore internet bots?
+    title: Ignoring internet bots
   - path: /guides/segment-vs-tag-managers
-    title: What is the difference between Segment and tag managers?
+    title: Segment vs. tag managers
   - path: /guides/what-is-replay
-    title: What is Replay?
+    title: Replay
 
   - section_title: How To Guides
     slug: guides/how-to-guides

src/guides/duplicate-data.md

@@ -1,5 +1,5 @@
 ---
-title: How does Segment handle duplicate data?
+title: Handling duplicate data
 ---
 
 Segment has a special de-duplication service that sits just behind the `api.segment.com` endpoint, and attempts to drop duplicate data. However, that de-duplication service has to hold the entire set of events in memory in order to know whether or not it has seen that event already. Segment stores 24 hours worth of event `message_id`s. This means Segment can de-duplicate any data that appears within a 24 hour rolling window.

src/guides/ignore-bots.md

@@ -1,20 +1,20 @@
 ---
-title: How can I ignore internet bots?
+title: Internet bots
 ---
 
-## But wait, I don't even know what a bot is!
+## What's a bot?
 
 If you stumbled onto this page by accident and don't know what a bot is or are just curious to learn more, the following Wikipedia article provides an awesome summary: [https://en.wikipedia.org/wiki/Internet\_bot](https://en.wikipedia.org/wiki/Internet_bot).
 
 Surprisingly, more than half of all web traffic is made up of bots. While a fraction of them are good bots with a regulated pattern, and therefore beneficial to all online businesses, the majority of them have malicious intents and are mostly unregulated.
 
-## Got it! So is it possible to ignore bad bots?
+## Is it possible to ignore bad bots?
 
-Now that we're level-set on what a bot is, unfortunately Segment does not offer any out-of-the-box feature to filter/ignore bot traffic.
+Segment doesn't offer any out-of-the-box feature to filter or ignore bot traffic.
 
 As such, you generally have two options:
 
-**Handle the filtering at a destination-level:** some of our destination partners, [like Mixpanel](https://help.mixpanel.com/hc/en-us/articles/115004567946-Exclude-Bot-Activity-Web-JavaScript-), filter bots automatically. Whereas others [such as Hubspot](https://knowledge.hubspot.com/getting-started-with-hubspot-v2/how-to-filter-out-traffic-from-your-website-analytics) allow you to set up bot filtering manually. The advantage of filtering bots at a destination level is that it allows you to implement a robust, easy-to-maintain solution. However, as it pertains to Segment, the downside is that bot traffic will _still_ make it to Segment, [affecting your MTU count.](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-does-segment-calculate-mtus)
+**Handle the filtering at a destination-level:** Some of Segment's destination partners, [like Mixpanel](https://help.mixpanel.com/hc/en-us/articles/115004567946-Exclude-Bot-Activity-Web-JavaScript-), filter bots automatically. Whereas others [such as Hubspot](https://knowledge.hubspot.com/getting-started-with-hubspot-v2/how-to-filter-out-traffic-from-your-website-analytics) allow you to set up bot filtering manually. The advantage of filtering bots at a destination level is that it allows you to implement a robust, easy-to-maintain solution. However, as it pertains to Segment, the downside is that bot traffic will _still_ make it to Segment, [affecting your MTU count.](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-does-segment-calculate-mtus)
 
 **Write custom logic that suppresses bot activity from being sent to Segment:** if you want to prevent bot traffic from making it to Segment in the first place, another option is to write your own custom code. The logic, in pseudo-code, would look something like this if you know a particular characteristic of the bot traffic to filter out, such as the userAgent:
 
@@ -25,17 +25,17 @@ if ! window.navigator.userAgent in robots
   analytics.track
 ```
 
-The benefit here of course is that you would be able to limit the impact that bots have on your MTU count. However, on the flip side, it's much harder to implement and maintain a custom filter.
+The benefit here is that you would be able to limit the impact that bots have on your MTU count. On the flip side, it's much harder to implement and maintain a custom filter.
 
-## If we see a massive MTU spike because of bots, can we apply for a refund?
+## If I see a massive MTU spike because of bots, can I apply for a refund?
 
-As a matter of policy, we typically do not provide refunds for bot-related MTU spikes, as bot traffic is out of our control. However for extenuating circumstances, [you can petition for a refund](https://segment.com/contact/billing), assuming you're able to provide proof of the bot's effect.
+As a matter of policy, Segment doesn't provide refunds for bot-related MTU spikes, as bot traffic is out of Segment's control. However for extenuating circumstances, [you can petition for a refund](https://segment.com/contact/billing), assuming you're able to provide proof of the bot's effect.
 
-## I'm seeing a lot of browser traffic from Boardman; isn't that from Segment?
+## I'm seeing a lot of browser traffic from Boardman; is that from Segment or a bot?
 
-We do indeed use Amazon's hosting services, which are based in Boardman, Oregon. However [many bots also originate from AWS in Boardman as well](https://productforums.google.com/forum/#!topic/webmasters/Ow5baxkjiPI).
+Segment uses Amazon's hosting services, which are based in Boardman, Oregon. However [many bots also originate from AWS in Boardman as well](https://productforums.google.com/forum/#!topic/webmasters/Ow5baxkjiPI).
 
-One way you can confirm whether or not traffic is coming from Segment vs. a bot is to check the userAgent of the inbound call. Ours is:
+One way you can confirm whether or not traffic is coming from Segment vs. a bot is to check the userAgent of the inbound call. Segment's is:
 
 ```js
 'Mozilla/5.0 (' + deviceModel.slice(0, -3) + '; CPU ' + osName + ' ' +

src/guides/intro-admin.md

@@ -1,5 +1,5 @@
 ---
-title: Segment for Workspace Administrators
+title: Segment for workspace administrators
 ---
 
 If your job is to set up or maintain a Segment Workspace for your organization, or assist other people using the Segment Web App, this guide is for you. If you're more interested in Segment implementation details, see the [developer intro guide](/docs/guides/intro-impl/).

src/guides/intro-impl.md

@@ -1,5 +1,5 @@
 ---
-title: Segment for Developers
+title: Segment for developers
 ---
 
 This guide explains all you need to know to get started with your Segment implementation, and directs you to more resources depending on your specific needs.

src/guides/intro-user.md

@@ -1,5 +1,5 @@
 ---
-title: Segment for Data Users
+title: Segment for data users
 ---
 
 If you aren't involved in setting up your Segment implementation, or are just starting to set up Destinations for your organization's workspace, this guide is for you.

src/guides/segment-vs-tag-managers.md

@@ -1,5 +1,5 @@
 ---
-title: What is the difference between Segment and tag managers?
+title: Segment vs. tag managers
 ---
 
 Tag managers, also known as Tag Management Systems (TMS), were a popular solution before the mainstream adoption of mobile apps. They primarily helped Digital Analytics and Online Marketers manage web tags or "beacons" on a website.

src/guides/what-is-replay.md

@@ -1,5 +1,5 @@
 ---
-title: What is Replay?
+title: Replay
 ---
 
 {% include content/plan-grid.md name="replay" %}