almost final

Author: spelluru

articles/stream-analytics/includes/event-generator-app.md

@@ -134,7 +134,7 @@ The next step is to define an input source for the job to read data using the ev
     1. For **Subscription**, select the Azure subscription where you created the event hub. The event hub can be in same or a different subscription as the Stream Analytics job.
     1. For **Event Hubs namespace**, select the Event Hubs namespace you created in the previous section. All the namespaces available in your current subscription are listed in the dropdown.
     1. For **Event hub name**, select the event hub you created in the previous section. All the event hubs available in the selected namespace are listed in the dropdown.
-    1. For **Event hub consumer group**, keep the **Create new** option selected so taht a new consumer group is created on the event hub. We recommend that you use a distinct consumer group for each Stream Analytics job. If no consumer group is specified, the Stream Analytics job uses the `$Default` consumer group. When a job contains a self-join or has multiple inputs, some inputs later might be read by more than one reader. This situation affects the number of readers in a single consumer group.
+    1. For **Event hub consumer group**, keep the **Create new** option selected so that a new consumer group is created on the event hub. We recommend that you use a distinct consumer group for each Stream Analytics job. If no consumer group is specified, the Stream Analytics job uses the `$Default` consumer group. When a job contains a self-join or has multiple inputs, some inputs later might be read by more than one reader. This situation affects the number of readers in a single consumer group.
     1. For **Authentication mode**, select **Connection string**. It's easier to test the tutorial with this option.  
     1. For **Event hub policy name**, select **Use existing**, and then select the policy you created earlier. 
     1. Select **Save** at the bottom of the page. 

articles/stream-analytics/media/stream-analytics-with-azure-functions/redis-cache-connection-string.png

@@ -52,7 +52,7 @@ Before you start, make sure you've completed the following steps:
 
 2. After you create the cache, under **Settings**, select **Access Keys**. Make a note of the **Primary connection string**.
 
-   ![Screenshot of Azure Cache for Redis connection string](./media/stream-analytics-with-azure-functions/image2.png)
+    :::image type="content" source="./media/stream-analytics-with-azure-functions/redis-cache-connection-string.png" alt-text="Screenshot showing the selection of the Access Key menu item.":::
 
 ## Create a function in Azure Functions that can write data to Azure Cache for Redis
 
@@ -171,7 +171,10 @@ Before you start, make sure you've completed the following steps:
 
 3. Provide a name for the output alias. In this tutorial, it's named **saop1**, but you can use any name of your choice. Fill in other details.
 
-4. Open your Stream Analytics job, and update the query to the following. If you didn't name your output sink **saop1**, remember to change it in the query.
+4. Open your Stream Analytics job, and update the query to the following. 
+
+    > [!IMPORTANT]
+    > If you didn't name your output sink **saop1**, remember to change it in the query.
 
    ```sql
     SELECT