[DOCS-7775] Fix wording and formatting

insight-engine/latest/admin/monitor.md

@@ -10,7 +10,7 @@ This task describes how to perform a full Solr reindex.
 
 The task assumes you are using only one Solr instance for all nodes in the Alfresco Content Services cluster. If not, then you need to repeat the process on each Solr instance used in the cluster.
 
-1. Confirm the location of the Solr core directories for archive and alfresco cores. This can be determined from the solrcore.properties file for both the cores. By default, the `solrcore.properties file` can be found at `<SOLR_HOME>/solrhome/alfresco/conf` or `<SOLR_HOME>/solrhome/archive/conf`. The Solr core location is defined in the `solrcore.properties` file as:
+1. Confirm the location of the Solr core directories for archive and alfresco cores. This can be determined from the `solrcore.properties` file for both the cores. By default, the `solrcore.properties file` can be found at `<SOLR_HOME>/solrhome/alfresco/conf` or `<SOLR_HOME>/solrhome/archive/conf`. The Solr core location is defined in the `solrcore.properties` file as:
 
     For Solr, the default data.dir.root path is:
 
@@ -130,7 +130,7 @@ The `SUMMARY` parameter provides the status of the tracking index and reports th
 * `Docs/Tx`: indicates summary statistics for the number of documents per transaction. It supports additional information with &detail=true, &hist=true and &value=true.
 * `Doc Transformation time (ms)`: indicates summary statistics for document transformation time. It supports additional information with &detail=true, &hist=true and &value=true.
 
-## Troubleshooting
+## Troubleshooting - transaction index failure
 
 Use this information to repair a transaction that failed to index.
 
@@ -177,21 +177,21 @@ Use the following setting to specify an option core for the report. If it is abs
 
 You can also fix index issues, check the index cache and backup individual indexes by using JMX. The status of the index can be checked using the JMX client on the **JMX MBeans > Alfresco > solrIndexes > `<store>`** tabs. The default view is the Solr core summary. The operations run the same consistency checks that are available by URL.
 
-### Troubleshooting - unsearchable content
+## Troubleshooting - unsearchable content
 
 If content becomes unsearchable for some documents, it is possible that the necessary transformations failed and the documents are currently indexed with a `transform_failed` status.
 
-> **Note:** For Enterprise installations (assuming the reason for these failed transformations is the temporary unavailability of the Transform Engines (T-Engines)) it is recommended to verify that the T-Engines do get back up and running, and to check that ActiveMQ was and still is available. In that case, the documents indexed with a `transform_failed` status should be automatically reindexed once the T-Engines come back up and the prior ActiveMQ messages are consumed, without any further steps being required.
+> **Note:** For Enterprise installations (assuming the reason for these failed transformations is the temporary unavailability of the Transform Engines (T-Engines)), it is recommended to verify that the T-Engines start running again, and to check that ActiveMQ is still available. In that case, the documents indexed with a `transform_failed` status should be automatically reindexed once the T-Engines start running again and the earlier ActiveMQ messages are consumed, without any further steps being required.
 
 These documents can be identified via the following query:
 
 ```http
 http://localhost:8080/solr/alfresco/select?indent=on&q=cm:content.transformationStatus:transform_failed&wt=xml
 ```
 
-You can extract the DB IDs of the nodes for the which the transformation of the content failed from the response:
+You can extract the DB IDs of the nodes for which the content transformation failed from the response:
 
-```
+```xml
     <result name="response" numFound="1" start="0">
         <doc>
             <long name="DBID">877</long>
@@ -219,9 +219,9 @@ Aug 22, 2011 8:19:21 PM org.apache.tomcat.util.net.jsse.JSSESupport handShake
 WARNING: SSL server initiated renegotiation is disabled, closing connection
 ```
 
-This message indicates that one side of the SSL connections is trying to renegotiate the SSL connection. This form of negotiation was found to be susceptible to man-in-the-middle attacks and it was disabled in the Java JSEE stack until a fix could be applied.
+This message indicates that one side of the SSL connections is trying to renegotiate the SSL connection. This form of negotiation was found to be susceptible to man-in-the-middle attacks and it was disabled in the Java JSEE stack until a fix could be applied.
 
-Refer to the following link for more information: [Transport Layer Security (TLS) Renegotiation Issue Readme](https://www.oracle.com/java/technologies/javase/tlsreadme2.html){:target="_blank"}.
+Refer to the following link for more information: [Transport Layer Security (TLS) Renegotiation Issue Readme](https://www.oracle.com/java/technologies/javase/tlsreadme2.html){:target="_blank"}.
 
 Refer also to the following links: