More fixes for indentation and layout

Author: garycentric

articles/stream-analytics/stream-analytics-real-time-fraud-detection.md

@@ -61,9 +61,9 @@ In this procedure, you first create an event hub namespace, and then you add an
 
 4. In the **Create namespace** pane, enter a namespace name such as `<yourname>-eh-ns-demo`. You can use any name for the namespace, but the name must be valid for a URL and it must be unique across Azure. 
 
-5. Select a subscription and create or choose a resource group, then click **Create**.
+5. Select a subscription and create or choose a resource group, then click **Create**.<br/><br/>
 
-    <img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-eventhub-namespace-new-portal.png" alt="Create event hub namespace in Azure portal" width="300px"/>
+    <br/><br/><img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-eventhub-namespace-new-portal.png" alt="Create event hub namespace in Azure portal" width="300px"/>
 
 6. When the namespace has finished deploying, find the event hub namespace in your list of Azure resources. 
 
@@ -73,7 +73,7 @@ In this procedure, you first create an event hub namespace, and then you add an
 
 8. Name the new event hub `asa-eh-frauddetection-demo`. You can use a different name. If you do, make a note of it, because you need the name later. You don't need to set any other options for the event hub right now.
 
-    <img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-eventhub-new-portal.png" alt="Name event hub in Azure portal" width="400px"/>
+    <br/><br/><img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-eventhub-new-portal.png" alt="Name event hub in Azure portal" width="400px"/>
 
 9. Click **Create**.
 
@@ -90,15 +90,15 @@ Before a process can send data to an event hub, the event hub must have a policy
 
 3. Add a policy named `asa-policy-manage-demo` and for **Claim**, select **Manage**.
 
-    <img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-shared-access-policy-manage-new-portal.png" alt="Create shared access policy for Stream Analytics" width="300px"/>
+    <br/><br/><img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-shared-access-policy-manage-new-portal.png" alt="Create shared access policy for Stream Analytics" width="300px"/>
 
 4. Click **Create**.
 
 5. After the policy has been deployed, click it in the list of shared access policies.
 
 6. Find the box labeled **CONNECTION STRING-PRIMARY KEY** and click the copy button next to the connection string. 
 
-    <img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-shared-access-policy-copy-connection-string-new-portal.png" alt="Stream Analytics shared access policy" width="300px"/>
+    <br/><br/><img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-shared-access-policy-copy-connection-string-new-portal.png" alt="Stream Analytics shared access policy" width="300px"/>
 
 7. Paste the connection string into a text editor. You need this connection string for the next section, after you make some small edits to it.
 
@@ -142,7 +142,7 @@ Before you start the TelcoGenerator app, you must configure it so that it will s
 
 2. Enter the following command:
 
-    ```cmd
+    ```console
     telcodatagen.exe 1000 0.2 2
     ```
 
@@ -178,7 +178,7 @@ Now that you have a stream of call events, you can set up a Stream Analytics job
 
     It's a good idea to place the job and the event hub in the same region for best performance and so that you don't pay to transfer data between regions.
 
-    <img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-sa-job-new-portal.png" alt="Create Stream Analytics job in portal" width="300px"/>
+    <br/><br/><img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-create-sa-job-new-portal.png" alt="Create Stream Analytics job in portal" width="300px"/>
 
 3. Click **Create**.
 
@@ -271,11 +271,11 @@ In many cases, your analysis doesn't need all the columns from the input stream.
 
 1. Change the query in the code editor to the following:
 
-   ```SQL
-   SELECT CallRecTime, SwitchNum, CallingIMSI, CallingNum, CalledNum 
-   FROM 
-       CallStream
-   ```
+    ```SQL
+    SELECT CallRecTime, SwitchNum, CallingIMSI, CallingNum, CalledNum 
+    FROM 
+        CallStream
+    ```
 
 2. Click **Test** again. 
 
@@ -289,13 +289,13 @@ For this transformation, you want a sequence of temporal windows that don't over
 
 1. Change the query in the code editor to the following:
 
-        ```SQL
-        SELECT 
-            System.Timestamp as WindowEnd, SwitchNum, COUNT(*) as CallCount 
-        FROM
-            CallStream TIMESTAMP BY CallRecTime 
-        GROUP BY TUMBLINGWINDOW(s, 5), SwitchNum
-        ```
+    ```SQL
+    SELECT 
+        System.Timestamp as WindowEnd, SwitchNum, COUNT(*) as CallCount 
+    FROM
+        CallStream TIMESTAMP BY CallRecTime 
+    GROUP BY TUMBLINGWINDOW(s, 5), SwitchNum
+    ```
 
     This query uses the `Timestamp By` keyword in the `FROM` clause to specify which timestamp field in the input stream to use to define the Tumbling window. In this case, the window divides the data into segments by the `CallRecTime` field in each record. (If no field is specified, the windowing operation uses the time that each event arrives at the event hub. See "Arrival Time Vs Application Time" in [Stream Analytics Query Language Reference](https://docs.microsoft.com/stream-analytics-query/stream-analytics-query-language-reference). 
 
@@ -317,19 +317,19 @@ When you use a join with streaming data, the join must provide some limits on ho
 
 1. Change the query in the code editor to the following: 
 
-        ```SQL
-        SELECT  System.Timestamp as Time, 
-            CS1.CallingIMSI, 
-            CS1.CallingNum as CallingNum1, 
-            CS2.CallingNum as CallingNum2, 
-            CS1.SwitchNum as Switch1, 
-            CS2.SwitchNum as Switch2 
-        FROM CallStream CS1 TIMESTAMP BY CallRecTime 
-            JOIN CallStream CS2 TIMESTAMP BY CallRecTime 
-            ON CS1.CallingIMSI = CS2.CallingIMSI 
-            AND DATEDIFF(ss, CS1, CS2) BETWEEN 1 AND 5 
-        WHERE CS1.SwitchNum != CS2.SwitchNum
-        ```
+	```SQL
+	SELECT  System.Timestamp as Time, 
+		CS1.CallingIMSI, 
+		CS1.CallingNum as CallingNum1, 
+		CS2.CallingNum as CallingNum2, 
+		CS1.SwitchNum as Switch1, 
+		CS2.SwitchNum as Switch2 
+	FROM CallStream CS1 TIMESTAMP BY CallRecTime 
+		JOIN CallStream CS2 TIMESTAMP BY CallRecTime 
+		ON CS1.CallingIMSI = CS2.CallingIMSI 
+		AND DATEDIFF(ss, CS1, CS2) BETWEEN 1 AND 5 
+	WHERE CS1.SwitchNum != CS2.SwitchNum
+	```
 
     This query is like any SQL join except for the `DATEDIFF` function in the join. This version of `DATEDIFF` is specific to Streaming Analytics, and it must appear in the `ON...BETWEEN` clause. The parameters are a time unit (seconds in this example) and the aliases of the two sources for the join. This is different from the standard SQL `DATEDIFF` function.
 
@@ -341,7 +341,7 @@ When you use a join with streaming data, the join must provide some limits on ho
 
 3. Click **Save** to save the self-join query as part of the Streaming Analytics job. (It doesn't save the sample data.)
 
-    <img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-query-editor-save-button-new-portal.png" alt="Save Stream Analytics query in portal" width="300px"/>
+    <br/><br/><img src="./media/stream-analytics-real-time-fraud-detection/stream-analytics-query-editor-save-button-new-portal.png" alt="Save Stream Analytics query in portal" width="300px"/>
 
 ## Create an output sink to store transformed data