fix lists

Author: ktoliver

articles/service-bus-messaging/service-bus-diagnostic-logs.md

@@ -28,8 +28,8 @@ Azure Service Bus currently supports activity/operational logs which capture **m
 
 All logs are stored in JavaScript Object Notation (JSON) format in the below 2 locations.
 
-1. **AzureActivity** - displays logs from operations/actions conducted against your namespace on the portal or through Azure Resource Manager template deployments.
-2. **AzureDiagnostics** - displays logs from operations/actions conducted against your namespace using the API, or through management clients on the language SDK.
+- **AzureActivity** - displays logs from operations/actions conducted against your namespace on the portal or through Azure Resource Manager template deployments.
+- **AzureDiagnostics** - displays logs from operations/actions conducted against your namespace using the API, or through management clients on the language SDK.
 
 Operational log JSON strings include elements listed in the following table:
 
@@ -61,7 +61,7 @@ Here's an example of an operational log JSON string:
 }
 ```
 
-## What Events/Operations are captured in operational logs?
+## What events/operations are captured in operational logs?
 
 Operation logs capture all management operations performed on the Azure Service Bus namespace. Data operations are not captured because of the high volume of data operations that are conducted on Azure Service Bus.
 
@@ -84,23 +84,23 @@ The below management operations are captured in operational logs -
 
 Operational logs are disabled by default. To enable diagnostic logs, perform the following steps:
 
-1.	In the [Azure portal](https://portal.azure.com), navigate to your Azure Service Bus namespace and under **Monitoring**, click **Diagnostics settings**.
+1. In the [Azure portal](https://portal.azure.com), navigate to your Azure Service Bus namespace and under **Monitoring**, click **Diagnostics settings**.
 
-	![blade navigation to diagnostic logs](./media/service-bus-diagnostic-logs/image1.png)
+   ![blade navigation to diagnostic logs](./media/service-bus-diagnostic-logs/image1.png)
 
 2. Click **Add diagnostic setting** to configure the diagnostic settings.  
 
-	![turn on diagnostic logs](./media/service-bus-diagnostic-logs/image2.png)
+   ![turn on diagnostic logs](./media/service-bus-diagnostic-logs/image2.png)
 
 3. Configure the diagnostic settings
-    1. Type a **name** to identify the diagnostic settings.
-    2. Pick a destination for the diagnostics.
-            1. If you pick **Storage account**, you need to configure the storage account where the diagnostics will be stored.
-            2. If you pick **Event hubs**, you need to configure the appropriate Event Hub where the diagnostics settings will be streamed to.
-            3. If you pick **Log Analytics**, you need to specify which instance of Log Analytics the diagnostics will be sent.
-        3. Check **Operational Logs**.
-
-	![change status diagnostic logs](./media/service-bus-diagnostic-logs/image3.png)
+   1. Type a **name** to identify the diagnostic settings.
+   2. Pick a destination for the diagnostics.
+      - If you pick **Storage account**, you need to configure the storage account where the diagnostics will be stored.
+      - If you pick **Event hubs**, you need to configure the appropriate Event Hub where the diagnostics settings will be streamed to.
+      - If you pick **Log Analytics**, you need to specify which instance of Log Analytics the diagnostics will be sent.
+    3. Check **OperationalLogs**.
+
+       ![change status diagnostic logs](./media/service-bus-diagnostic-logs/image3.png)
 
 4. Click **Save**.