format codeblocks

src/content/docs/apm/agents/java-agent/troubleshooting/no-data-appears-java.mdx

@@ -31,13 +31,13 @@ After sending a request to your web application, data should appear in the APM U
 
       Linux or macOS:
 
-      ```
+      ```sh
       ps -ef | grep java
       ```
 
       Windows:
 
-      ```
+      ```sh
       wmic process where "name='java.exe'" get ProcessID, Commandline /format:list
       ```
    3. Find the process for the service you're trying to monitor and see if the `-javaagent` argument is present:
@@ -50,7 +50,7 @@ After sending a request to your web application, data should appear in the APM U
 6. Check the application server logs for errors related to the New Relic Java agent. You can see the troubleshooting pages [Error bootstrapping Java agent](/docs/agents/java-agent/troubleshooting/error-bootstrapping-new-relic-java-agent) and [Errors starting Java app server](/docs/agents/java-agent/troubleshooting/errors-starting-java-app-server) for examples of observable errors in application server logs that prevent the java agent data from reporting.
 7. Verify that your app is reporting to the expected name: In your New Relic log files, search for `"reporting to"`, then select the link in the message. For example:
 
-   ```
+   ```json
    {"message":"Reporting to: https://rpm.newrelic.com/accounts/000/applications/000000"}
    ```