Updates to script and link for YouTube plugin + Sendgrid docs

src/connections/destinations/catalog/freshsales-suite-crm/index.md

@@ -36,7 +36,7 @@ You can use identify to create a contact when a website visitor fills a webform.
 
 userId is a mandatory field which is used to identify the contact in Freshsales. If your user identifier is not email, then email has to be a part of traits.
 
-```json=
+```json
 {
   "userId": "97980cfea0067",
   "type": "identify",
@@ -78,7 +78,7 @@ Custom fields won't automatically create. You have to create them in Freshsales
 
 You can also update Accounts and Deals associated with a contact in Freshsales. The company and deal objects in the identify payload correspond to the Accounts and Deals objects in Freshsales. When you use the identify method to create a contact, it's possible to also create the corresponding Account and Deal and Freshsales. To do this, pass the company or the deal objects within traits in the identify call.
 
-```json=
+```json
 {
   "userId" : "97980cfea0067",
   "type": "identify",
@@ -101,7 +101,7 @@ You can also update Accounts and Deals associated with a contact in Freshsales.
 
 You can track activities of your website visitors. If a user is subscribing to a newsletter and you want to track it, use the track method.
 
-```json=
+```json
 {
   "userId" : "john.doe@example.com",
   "event": "Email Bounced",
@@ -121,15 +121,16 @@ Segment standardized a series of reserved event names that have special semantic
 
 If you want to track users visiting your sites, you can use the page method. When you call a page event, Segment sends a pageview to Freshsales. You can send extra data parameters within properties in the event payload. [See the reserved properties for more details](/docs/connections/spec/page/#properties).
 
-```json=
+```json
 {
-  "userId" : "john.doe@example.com",
+  "userId": "john.doe@example.com",
   "name": "Page view",
-  “type”: ”page”, 
-  "properties" : {
+  "type": "page",
+  "properties": {
     "title": "Welcome to pricing page | Example.com",
-    "url" : "http://example.com/pricing"
+    "url": "http://example.com/pricing"
   }
+}
 ```
 
 ## FAQs

src/connections/sources/catalog/cloud-apps/sendgrid-marketing-campaigns/index.md

@@ -3,7 +3,7 @@ title: SendGrid Marketing Campaigns Source
 id: GCeG0vmcDW
 ---
 
-[SendGrid Marketing Campaigns](http://twilio.com/docs/sendgrid/ui/integrations/segment?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} lets you automatically stream your email events directly into Segment for use inside your warehouse or other downstream destinations.
+[SendGrid Marketing Campaigns](https://twilio.com/docs/sendgrid/ui/integrations/segment?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} lets you automatically stream your email events directly into Segment for use inside your warehouse or other downstream destinations.
 
 This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) that can not only export data into your Segment warehouse but also federate the exported data into your other enabled Segment destinations.
 

src/connections/sources/catalog/libraries/website/plugins/youtube/index.md

@@ -3,7 +3,7 @@ title: analytics.js YouTube Plugin
 hidden: true
 ---
 
-With the analytics.js YouTube Plugin you can collect YouTube player events into the Segment ecosystem.
+With the analytics.js YouTube Plugin, you can collect YouTube player events into the Segment ecosystem.
 
 The Segment YouTube Plugin uses the following Google APIs:
 - [YouTube IFrame player API](https://developers.google.com/youtube/iframe_api_reference#Getting_Started){:target="_blank”}: Controls the video (play, pause, stop).
@@ -16,19 +16,19 @@ To begin, create a new project in the Google Developer Console, then create a ne
 > warning "Secure your API keys"
 > You can [secure your API keys](https://cloud.google.com/docs/authentication/api-keys#securing){:target="_blank”} by adding API key restrictions, deleting unused API keys, and periodically rotating your keys. 
 
-## Getting Started
+## Getting started
 
 After you've generated the API key:
 
 1. Enable a new plugin.
 
     - Navigate to **Connections > Sources** and choose the source you want to connect the YouTube plugin to. Go to the **Settings** tab of your source and select **Plugins**. You can enable the YouTube plugin from this menu:
 
-    ![the plugins setting screen](./images/youtube-vimeo-plugins-beta-2021-06-04.png)
+    ![Screenshot of the plugins setting screen](./images/youtube-vimeo-plugins-beta-2021-06-04.png)
 
     **Note:** Only JavaScript sources support plugins.
 
-2. Initialize the plugin by giving it access to the YouTube video player instance(s) running on your page. This can be done by adding this script,  <script src="https://www.youtube.com/iframe_api"></script> to the section of the source code where the page loads.
+2. Initialize the plugin by giving it access to the YouTube video player instance(s) running on your page. This can be done by adding the following script to the section of the source code where the page loads.
 
     - Use the initialize method in the YouTube `onYouTubeIframeAPIReady()` function to register and initialize the plugin with the player instance and your API key:
 
@@ -48,7 +48,7 @@ var player;
 
 The plugin listens to the YouTube player for events, and fires the corresponding [Segment Video Spec](/docs/connections/spec/video/) events on analytics.js.
 
-## Supported Events
+## Supported events
 The plugin tracks the following [Segment Video Spec](/docs/connections/spec/video/) events:
 
 Event | Details
@@ -60,17 +60,17 @@ Video Playback Buffer Started/Completed | When playback starts and finishes buff
 Video Playback Seek Started/Completed | When a user manually seeks a certain position of the content or ad in the playback.
 Video Content Started/Completed | When a video content segment starts and completes playing within a playback. <br><br>- If playing a playlist, these events get fired for each individual video.
 
-## Supported Properties
-The plugin automatically attaches the following [Segment Video Spec](/docs/connections/spec/video/) to the above events:
+## Supported properties
+The plugin automatically attaches the following [Segment Video Spec](/docs/connections/spec/video/) to [supported events](#supported-events):
 
-**'Playback' Events**
+**'Playback' events**
 - Total Length
 - Position
 - Quality
 - Video Player
 - Sound
 
-**'Content' Events**
+**'Content' events**
 - Title
 - Description
 - Keywords