docs: attempt to fix code formatting

attempt #2 to fix the code formatting, it's unclear why the first line in this example is not getting it's indentation:

```cs
    async Task<string> WebEndpointExample()
    {
        var task = DoSomethingForSomeSecondsAsync(5); //kick off a 5-second-work to be done.
        
        //Do something less than 5 seconds here.
    
        await task;
        return "Complete";
    }

    [Trace]
    [MethodImpl(MethodImplOptions.NoInlining)]
    private static async Task DoSomethingForSomeSecondsAsync(int seconds)
    {
        await Task.Delay(TimeSpan.FromSeconds(seconds));
    }
```

src/content/docs/apm/agents/net-agent/other-features/async-support-net.mdx

@@ -97,7 +97,7 @@ Here is a summary of known limitations for async instrumentation with our .NET a
   >
   It is expected for response time to be less than the total time spent in `async`-`await` usage scenerios. Consider the following code example for a web endpoint:
 
-```cs
+    ```cs
     async Task<string> WebEndpointExample() 
     {
         await DoSomethingForSomeSecondsAsync(5); //kick off a 5-second-work to be done.
@@ -110,7 +110,7 @@ Here is a summary of known limitations for async instrumentation with our .NET a
     {
         await Task.Delay(TimeSpan.FromSeconds(seconds));
     }
-```
+    ```
 
   In this code example, it takes approximately 5 seconds for the `WebEndpointExample` to complete, so the response time for the transaction that represents the request to the `WebEndpointExample` endpoint will be approximately 5 seconds.
 
@@ -122,7 +122,7 @@ Here is a summary of known limitations for async instrumentation with our .NET a
 
   At the same time, the agent cannot assume calling to `async` methods would always block the caller for the entire time. The next example demonstrates this:
 
-```cs
+    ```cs
     async Task<string> WebEndpointExample()
     {
         var task = DoSomethingForSomeSecondsAsync(5); //kick off a 5-second-work to be done.
@@ -139,7 +139,7 @@ Here is a summary of known limitations for async instrumentation with our .NET a
     {
         await Task.Delay(TimeSpan.FromSeconds(seconds));
     }
-```
+    ```
 
   In this example, the response time is still approximately 5 seconds, but the actual execution time of the `WebEndpointExample` is no longer approximately 0.
   </Collapser>