alt text qa

- Removed quotes
- Added periods to the end of alt-text
- Removed colors of boxes, arrows, etc.
- Fixed spelling errors

diagram-library/readme.md

@@ -4,7 +4,7 @@ The library file was built by Tonik, and is in Sketch. You'll need a Sketch lice
 
 You can also export the file, or diagrams you make with it, to `.svg` format for storage.
 
-![Diagram showing how data is transferred from Segment Tracking API to a customer's AWS S3 bucket](sample-diagram.png)
+![Diagram showing how data is transferred from Segment Tracking API to a customer's AWS S3 bucket.](sample-diagram.png)
 
 ## Using the Library
 

src/connections/destinations/catalog/activecampaign/index.md

@@ -78,7 +78,7 @@ ActiveCampaign also supports updating a contact's custom fields with this integr
 
 For example, if you have a contact in ActiveCampaign with these custom fields:
 
-![A screenshot of the fields page in ActiveCampaign, featuring two custom fields: Shirt Size and State](images/jda1490xo_screenshot2015-12-07at3.58.27pm.png)
+![A screenshot of the fields page in ActiveCampaign, featuring two custom fields: Shirt Size and State.](images/jda1490xo_screenshot2015-12-07at3.58.27pm.png)
 
 You can update those fields using this identify call:
 

src/connections/destinations/catalog/adobe-analytics/identity.md

@@ -9,14 +9,14 @@ The Identity Resolution destination settings are:
 - **Marketing Cloud ID**
 - **Drop VisitorID**, and **No Fallbacks for VisitorID:Server-Side Only** destination settings.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Identity Resolution section selected](images/identity-resolution.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Identity Resolution section selected.](images/identity-resolution.png)
 
 The Timestamp destination settings are:
 - **Timestamp Option**
 - **Send Both Timestamp and VisitorID for Timestamp Optional Reporting Suites**
 - **Prefer VisitorID for Hybrid Timestamp Reporting**
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Timestamps section selected](images/timestamps.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Timestamps section selected.](images/timestamps.png)
 
 ## Analytics.js - Device Mode
 
@@ -65,4 +65,4 @@ If **No Fallbacks for Visitor ID** is enabled, and you're setting a `marketingCl
 
 This decision tree is a visual representation of how Segment's Adobe Analytics destination settings and payload data interact with Segment to determine when to send a `visitorId` to Adobe.
 
-![A decision tree outlining when and how visitorId is sent from Segment, as outlined in section above](images/adobe-identity-res-decision-tree.png)
+![A decision tree outlining when and how visitorId is sent from Segment, as outlined in the section above.](images/adobe-identity-res-decision-tree.png)

src/connections/destinations/catalog/adobe-analytics/settings.md

@@ -355,7 +355,7 @@ The Segment Adobe Analytics Merchandising setting runs as follows:
 
 Let's take the following example:
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the "Merchandising" tab. Two properties from the "eVar" tab are also included on this screenshot.](images/merchandising-event.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the "Merchandising" tab. Two properties from the "eVar" tab are also included in this screenshot.](images/merchandising-event.png)
 
 The configuration in the example image above configures an `Order Completed` Segment event which sends Adobe Analytics:
 - `event1` in `s.events` with the value passed from `properties.increment`.

src/connections/destinations/catalog/adroll/index.md

@@ -13,7 +13,7 @@ id: 54521fd525e721e32a72ee8e
 2. Search for "Adroll" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Locate both your AdRoll Advertiser ID and Pixel ID in AdRoll's "Audience" tab, "AdRoll Pixel" section. Click on "View Pixel". Your Advertiser ID will be listed beside `adroll_adv_id` and your AdRoll Pixel will be listed beside `adroll_pix_id`.
 
-    ![A screenshot of the Adroll Audience page, with Site Audiences selected. A green arrow points to the Adroll Pixel "View Pixel" button.](images/adroll-pixel.png)
+    ![A screenshot of the Adroll Audience page, with Site Audiences selected. An arrow points to the Adroll Pixel "View Pixel" button.](images/adroll-pixel.png)
 
 4. Add both your Advertiser ID and Pixel ID to your Segment Destination Settings.
 

src/connections/destinations/catalog/amazon-lambda/index.md

@@ -31,15 +31,15 @@ To build a Lambda function:
 1. Go to the Lambda service page in your AWS account.
 2. Click **Create a function** to create a new function.
 
-    ![A screenshot of the AWS Lambda service page, with a red box around the "Create a function" button.](images/LambdaDashboard.png)
+    ![A screenshot of the AWS Lambda service page, with a box around the "Create a function" button.](images/LambdaDashboard.png)
 
 3. Select **Author from scratch** since Segment will be providing the source code for the function.
 4. Enter a name for your function and select your preferred runtime.
 5. For the **Role** field, select **Create a new role from AWS policy templates** from the dropdown.
 6. Create a **Role name** and leave **Policy templates** empty. This will create a role that can write to Cloud Watch logs. Cloud Watch logs are optional, though Segment supports them in the Segment settings.
 7. Click **Create function**.
 
-    ![A screenshot of the AWS Lambda function settings page](images/LambdaCreateFunction.png)
+    ![A screenshot of the AWS Lambda function settings page.](images/LambdaCreateFunction.png)
 
 8. Copy the **ARN** for the Lambda and paste it into the **Lambda** setting in your Segment Lambda destination settings.
 
@@ -63,17 +63,17 @@ Using CloudFormation minimizes the setup steps needed, and is Segment's recommen
 2. Create the CloudFormation stack.
    1. Within the AWS Console, navigate to **CloudFormation > Stacks**.
 
-      ![A screenshot of the CloudFormation dropdown in AWS, with "Stacks" selected](images/CloudFormationStackNav.png)
+      ![A screenshot of the CloudFormation dropdown in AWS, with "Stacks" selected.](images/CloudFormationStackNav.png)
 
    2. Click **Create Stack**.
 
-      ![A screenshot of the CloudFormation Stacks page in AWS, with the "Create Stack" button visible](images/CloudFormationCreateStack.png)
+      ![A screenshot of the CloudFormation Stacks page in AWS, with the "Create Stack" button visible.](images/CloudFormationCreateStack.png)
 
    3. On the **Select Template** page, select **Upload a template to Amazon S3**. Using **Choose File**, select the SegmentLambdaDestinationCFTemplate you downloaded in the previous step.
 
    4. Click **Next**.
 
-      ![A screenshot of the CloudFormation Select Template settings page, with ](images/CloudFormationUploadTemplate.png)
+      ![A screenshot of the CloudFormation Select Template settings page.](images/CloudFormationUploadTemplate.png)
 
    5. Give your stack a name.
    6. For the **ExternalId** parameter, enter the "External ID" setting in your Segment Lambda destination settings.
@@ -86,19 +86,19 @@ Using CloudFormation minimizes the setup steps needed, and is Segment's recommen
    9. On the last page, review your template details and click **Create**.
    10. You will now see your new Stack listed in the Stacks page.
 
-        ![A screenshot of the Stacks page, with a Stack named SegmentLambdaRoleTest visible](images/CloudFormationCreateInProgress.png)
+        ![A screenshot of the Stacks page, with a Stack named SegmentLambdaRoleTest visible.](images/CloudFormationCreateInProgress.png)
 
    11. Once the status is **CREATE_COMPLETE**, click on the name of your Stack.
    12. On the Stack Detail page under the **Resources** section, you will see a policy and role listed.
 
-        ![A screenshot of the Resources section of the Stack Detail page, with a invokeLambdaPolicy and an invokeLambdaRole visible](images/CloudFormationLambdaRole.png)
+        ![A screenshot of the Resources section of the Stack Detail page, with a invokeLambdaPolicy and an invokeLambdaRole visible.](images/CloudFormationLambdaRole.png)
 
    13. Click the **Physical ID** of the role. You will be redirected to the summary page for the role within the IAM console.
    14. Copy the **Role ARN** and copy it into the **Role Address** setting in your Segment Lambda destination settings.
 
 Using the examples provided, your Segment Lambda destination settings will look something like this:
 
-![A screenshot of the connection settings page in Segment, with information visible in the Lambda, Region, and Role Address fields](images/SegmentLambdaSettingsPostCF.png)
+![A screenshot of the connection settings page in Segment, with information visible in the Lambda, Region, and Role Address fields.](images/SegmentLambdaSettingsPostCF.png)
 
 
 #### Create Policy and Role Manually
@@ -143,7 +143,7 @@ To create an IAM role:
 5. Search for and select your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home){:target="_blank"}.
 6. Select the **Trust Relationships** tab, then click **Edit trust relationship**.
 
-    ![A screenshot of the AWS IAM home summary, with the Trust relationships tab selected](images/LambdaTrustRelationship.png)
+    ![A screenshot of the AWS IAM home summary, with the Trust relationships tab selected.](images/LambdaTrustRelationship.png)
 
 7. Copy and paste the following code into your trust relationship. You should replace `<your-source-id>` with either the Source ID of the attached Segment source (the default) or the External ID set in your AWS Lambda destination settings.
   * `arn:aws:iam::595280932656:root` refers to Segment's AWS Account, and is what allows Segment's Destination to access the role to invoke your Lambda.