more fixes

Author: stayseesong

src/_includes/content/connection-modes-intro.md

@@ -5,5 +5,10 @@ Segment's web source (Analytics.js), and native client-side libraries (iOS, Andr
 - **Device-mode**: You include additional code on your website or mobile app which allows Segment to use the data you collect on the device to make calls directly to the destination tool's API, without sending it to the Segment servers _first_. (You still send your data to the Segment servers, but this occurs asynchronously.) This is also called *wrapping* or *bundling*, and it might be required when the source has to be loaded on the page to work, or loaded directly on the device to function correctly. When you use Analytics.js, you can change the device-mode destinations that a specific source sends from within the Segment web app, without touching any code.
 
 
-> info ""
-> If you use Server source libraries, they only send data directly to Segment in Cloud-mode. (Server library implementations operate in the server backend, and can't load additional destination SDKs.)
+<div class="premonition info">
+  <div class="fa fa-info-circle"></div>
+  <div class="content">
+    <p class="header"></p>
+    <p>If you use Server source libraries, they only send data directly to Segment in Cloud-mode. Server library implementations operate in the server backend, and can't load additional destination SDKs.</p>
+  </div>
+</div>

src/connections/destinations/destination-filters.md

@@ -86,11 +86,11 @@ This example shows a rule that only sends track calls to Google Analytics.
 
 ### Remove internal and test events from production tools
 
-This rule targets email addresses with internal domains to stop test events from reaching Destinations.
+In the example below, the rule targets email addresses with internal domains to stop test events from reaching Destinations.
 
 ![Example of a filter that removes internal and test events from production tools](images/destination-filters/internal_example.png)
 
-This rule prevents an event from sending if `Order Completed` and `properties.email` contain an internal `@segment.com` email address.
+In the example below, the rule prevents an event from sending if `Order Completed` and `properties.email` contain an internal `@segment.com` email address.
 
 ![Internal domain filter example](images/destination-filters/internal_example2.png)
 
@@ -116,7 +116,7 @@ Segment makes effort to ensure that Destination Filters can handle unexpected si
 
 Errors aren't exposed in your Destination's Event Deliverability tab. For help diagnosing missing destination filter events, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
 
-## FAQ
+## FAQs
 
 #### How do Destination Filters work with array properties?
 
@@ -134,7 +134,7 @@ To block the Identify event trait `products.newElement`, select the option under
 
 Segment supports 10 filters per destination. If you need help consolidating filters or would like to discuss your use case, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
 
-#### Can I set multiple `Only Send` Destination Filters?
+#### Can I set multiple `Only Send` destination filters?
 
 Segment evaluates multiple `Only Send` filters against each other and resolves Destination Filters in order. If multiple `Only Send` filters conflict with each other, Segment won't send information downstream.
 
@@ -156,7 +156,7 @@ The Activity Feed shows the action, date, and user who performed the action when
 
 #### Why am I getting a permissions denied error when I try to save a filter?
 
-You must have write access to save and edit filters. Read permission only allows viewing and testing access.
+You must have write access to save and edit filters. Read permission access only allows viewing and testing access.
 
 #### How can I test my filter?
 

src/connections/destinations/index.md

@@ -11,7 +11,7 @@ If you want to explore the destinations compatible with Segment, check out the [
 
 Segment has [Sources](/docs/connections/sources/) and [Destinations](/docs/connections/destinations/). Sources send data _into_ Segment, while Destinations receive data _from_ Segment.
 
-## Types of sources
+### Types of sources
 
 Segment has five types of sources: Web (Analytics.js), Mobile, Server, Cloud App, and User-created [Source Functions](/docs/connections/sources/source-functions/). Web, Mobile, and Server sources send first-party data from your digital properties. Cloud-app sources send data about your users from your connected web apps, such as [Zendesk](/docs/connections/sources/catalog/cloud-apps/zendesk/), [Stripe](/docs/connections/sources/catalog/cloud-apps/stripe/), or [Braze](/docs/connections/sources/catalog/cloud-apps/braze/).
 
@@ -36,7 +36,7 @@ In June 2021, Segment released a new form of destinations called [Destinations A
 {% include content/connection-modes-intro.md %}
 
 
-### When should I use Device-mode? When should I use Cloud-mode?
+### How Segment determines Device-mode and Cloud-mode destinations
 
 There are two main things Segment considers when deciding to use Device-mode or Cloud-mode, or both, for a destination partner:
 1. [Anonymous Attribution Methodology](#anonymous-attribution-methodology)
@@ -48,7 +48,7 @@ There are two main things Segment considers when deciding to use Device-mode or
 
 The anonymous identifiers used on mobile devices are usually static, which means Segment doesn't need to do additional resolution, and can build Cloud-mode destinations by default. Because Segment uses native advertising identifiers on mobile devices, you don't need a full SDK on the device to reconcile or identify a user. For example, you might track users who viewed an advertisement in one app and installed another app as a result.
 
-However, some mobile attribution tools do more advanced reconciliation based on more than the native identifier, which requires the SDK on the device to work properly. For those destinations, Segment offers device-mode which packages the tool's SDK with the client-side library, so that you can get the entire range of tool functionality.
+However, some mobile attribution tools do more advanced reconciliation based on more than the native identifier, which requires the SDK on the device to work properly. For those destinations, Segment offers device-mode, which packages the tool's SDK with the client-side library so that you can get the entire range of tool functionality.
 
 ##### Web Attribution