Apply suggestions from code review

Co-authored-by: Karl Erickson <[email protected]>

Author: JoshTheTechWriter

articles/spring-apps/basic-standard/concept-app-status.md

@@ -73,7 +73,7 @@ The instance status is reported as one of the following values:
 
 | Value       | Definition |
 |-------------|------------|
-| Starting    | The binary is successfully deployed to the given instance. The instance booting the .**jar** file might fail because the **.jar** file can't run properly. Azure Spring Apps restarts the app instance in 60 seconds if it detects that the app instance is still in the **Starting** state. |
+| Starting    | The binary is successfully deployed to the given instance. The instance booting the **.jar** file might fail because the **.jar** file can't run properly. Azure Spring Apps restarts the app instance in 60 seconds if it detects that the app instance is still in the **Starting** state. |
 | Running     | The instance works. The instance can serve requests from inside Azure Spring Apps. |
 | Failed      | The app instance failed to start the user's binary after several retries. The app instance might be in one of the following states:<br/>- The app might stay in the **Starting** status and never be ready for serving requests.<br/>- The app might boot up but crash in a few seconds. |
 | Terminating | The app instance is shutting down. The app might not serve requests and the app instance is removed. |

articles/spring-apps/basic-standard/how-to-appdynamics-java-agent-monitor.md

@@ -219,7 +219,7 @@ You can define more metrics for the JVM, as shown in this screenshot of the **Me
 
 ## View AppDynamics Agent logs
 
-By default, Azure Spring Apps prints the info level logs of the AppDynamics Agent to `STDOUT`. The logs are mixed with the application logs. You can find the explicit agent version from the application logs.
+By default, Azure Spring Apps prints the *info* level logs of the AppDynamics Agent to `STDOUT`. The logs are mixed with the application logs. You can find the explicit agent version from the application logs.
 
 You can also get the logs of the AppDynamics Agent from the following locations:
 

articles/spring-apps/basic-standard/how-to-capture-dumps.md

@@ -87,7 +87,7 @@ Use the following steps to generate a heap or thread dump of your app in Azure S
 
 ## Get your diagnostic files
 
-Navigate to the target file path in your persistent storage and find your dump/JFR. From there, you can download them to your local machine. The name of the generated file will be similar to `<app-instance>_heapdump_<time-stamp>.hprof` for the heap dump, `<app-instance>_threaddump_<time-stamp>.txt` for the thread dump, and `<app-instance>_JFR_<time-stamp>.jfr` for the JFR file.
+Navigate to the target file path in your persistent storage and find your dump/JFR. From there, you can download them to your local machine. The name of the generated file will be similar to **\<app-instance>_heapdump_\<time-stamp>.hprof** for the heap dump, **\<app-instance>_threaddump_\<time-stamp>.txt** for the thread dump, and **\<app-instance>_JFR_\<time-stamp>.jfr** for the JFR file.
 
 ## Next steps
 

articles/spring-apps/basic-standard/how-to-custom-persistent-storage.md

@@ -187,11 +187,11 @@ This section addresses frequently asked questions about using your own persisten
 
 - If I have built-in persistent storage enabled, and then I enabled my own storage as extra persistent storage, is my data migrated into my Azure Storage account?
 
-   No. But we're going to provide a document to help you do the migration yourself soon.
+   *No. But we're going to provide a document to help you do the migration yourself soon.*
 
 - What are the reserved mount paths?
 
-  Azure Spring Apps reserves the following mount paths:
+  *Azure Spring Apps reserves the following mount paths:*
 
   - **/tmp**
   - **/persistent**