couple of tweaks ahead of pre-review

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/durable-task-scheduler/troubleshoot-durable-task-scheduler.md

@@ -2,7 +2,7 @@
 title: Troubleshoot the Azure Functions durable task scheduler dashboard (preview)
 description: Learn how to troubleshoot error messages and issues you encounter while using the Azure Functions durable task scheduler.
 ms.topic: conceptual
-ms.date: 01/27/2025
+ms.date: 03/18/2025
 ---
 
 # Troubleshoot the Azure Functions durable task scheduler dashboard (preview)
@@ -13,23 +13,22 @@ When your app isn't running as expected, first check if you have the correct con
 
 ### Local development
 
-1. Check connection string, which should have this format: `Endpoint=http://localhost:<port number>;Authentication=None`. Ensure the port number is the one mapped to `8080` on the [container that's running the emulator](./quickstart-durable-task-scheduler.md#set-up-durable-task-scheduler-emulator). 
-1. In addition to the durable task scheduler emulator, check that the Azure Storage emulator [Azurite is started](./quickstart-durable-task-scheduler.md#test-locally). Azurite is need for components of the app related to Functions. 
+1. Check the connection string, which should have this format: `Endpoint=http://localhost:<port number>;Authentication=None`. Ensure the port number is the one mapped to `8080` on the [container running the durable task scheduler emulator](./quickstart-durable-task-scheduler.md#set-up-durable-task-scheduler-emulator). 
+
+1. Along with the durable task scheduler emulator, make sure [the Azure Storage emulator, Azurite, is started](./quickstart-durable-task-scheduler.md#test-locally). Azurite is needed for components of the app related to Functions. 
 
 ### Running on Azure
 
 1. Check your app for the environment variables `DURABLE_TASK_SCHEDULER_CONNECTION_STRING` and `TASKHUB_NAME`.
-1. Check the value of `DURABLE_TASK_SCHEDULER_CONNECTION_STRING`. Specifically, verify that the scheduler endpoint and authentication type are correct. The connection string should be formatted as follows when using: 
-
-    *User-assigned managed identity*
 
-    `Endpoint={scheduler endpoint};Authentication=ManagedIdentity;ClientID={client id}`, where *client id* is the identity's client ID. 
+1. Check the value of `DURABLE_TASK_SCHEDULER_CONNECTION_STRING`. Specifically, verify that the scheduler endpoint and authentication type are correct. The connection string should be formatted as follows when using: 
 
-    *System-assigned managed identity*
+    - *User-assigned managed identity*: `Endpoint={scheduler endpoint};Authentication=ManagedIdentity;ClientID={client id}`, where *client id* is the identity's client ID. 
+    - *System-assigned managed identity*: `Endpoint={scheduler endpoint};Authentication=ManagedIdentity`
 
-    `Endpoint={scheduler endpoint};Authentication=ManagedIdentity`
 1. Ensure the required role-based access control (RBAC) permission is [granted to the identity](./develop-with-durable-task-scheduler.md#configure-identity-based-authentication-for-app-to-access-durable-task-scheduler) needing to access the specified task hub or scheduler. 
-  1. When accessing the dashboard, ensure permission is [assigned to your own identity (email)](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard).
+  -  When accessing the dashboard, ensure permission is [assigned to your own identity (email)](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard).
+
 1. If user-assigned managed identity is used, ensure the [identity is assigned to your app](./develop-with-durable-task-scheduler.md#assign-managed-identity-to-your-app).
 
 ## Error deploying durable functions app to Azure 
@@ -41,6 +40,7 @@ If your deployment fails with an error such as `Encountered an error (ServiceUna
 If you get an `Unknown error retrieving details of this task hub` error on the durable task scheduler dashboard, the reason could be:
 
 1. Your identity (email) doesn't have the required permission assigned for that task hub. Follow instructions to [grant the permission](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard), then access the dashboard again. 
+
 1. Your task hub was deleted. 
 
 ## Can't delete resource
@@ -97,17 +97,17 @@ For Mx Mac (ARM64) users, you may run into gRPC runtime issues with durable func
 1. Reference the `2.41.0` version of the `Contrib.Grpc.Core.M1` NuGet package.
 1. Add a custom after-build target that ensures the correct ARM64 version of the gRPC libraries can be found.
 
-```xml
-<Project>
-  <ItemGroup>
-    <PackageReference Include="Contrib.Grpc.Core.M1" Version="2.41.0" />
-  </ItemGroup>
-
-  <Target Name="CopyGrpcNativeAssetsToOutDir" AfterTargets="Build">
-    <ItemGroup>
-       <NativeAssetToCopy Condition="$([MSBuild]::IsOSPlatform('OSX'))" Include="$(OutDir)runtimes/osx-arm64/native/*"/>
-    </ItemGroup>
-    <Copy SourceFiles="@(NativeAssetToCopy)" DestinationFolder="$(OutDir).azurefunctions/runtimes/osx-arm64/native"/>
-  </Target>
-</Project>     
-``` 
+   ```xml
+   <Project>
+     <ItemGroup>
+       <PackageReference Include="Contrib.Grpc.Core.M1" Version="2.41.0" />
+     </ItemGroup>
+   
+     <Target Name="CopyGrpcNativeAssetsToOutDir" AfterTargets="Build">
+       <ItemGroup>
+          <NativeAssetToCopy Condition="$([MSBuild]::IsOSPlatform('OSX'))" Include="$(OutDir)runtimes/osx-arm64/native/*"/>
+       </ItemGroup>
+       <Copy SourceFiles="@(NativeAssetToCopy)" DestinationFolder="$(OutDir).azurefunctions/runtimes/osx-arm64/native"/>
+     </Target>
+   </Project>     
+   ```