Minor edits to correlation id guide

doc/administration/troubleshooting/tracing_correlation_id.md

@@ -31,10 +31,10 @@ documenation for some popular browsers.
 To locate a relevant request and view its correlation ID:
 
 1. Enable persistent logging in your network monitor. Some actions in GitLab will redirect you quickly after you submit a form, so this will help capture all relevant activity.
-1. To help isolate the requests you are looking for, you can filter for "document" requests.
+1. To help isolate the requests you are looking for, you can filter for `document` requests.
 1. Click the request of interest to view further detail.
-1. Go to the "headers" section and look for _response_ headers. There you should find an `x-request-id` header with a
-randomly generated value.
+1. Go to the **Headers** section and look for **Response Headers**. There you should find an `x-request-id` header with a
+value that was randomly generated by GitLab for the request.
 
 See the following example:
 
@@ -53,7 +53,7 @@ interested in.
 
 ### Getting the correlation ID from curl
 
-If you're using curl then you can use the verbose option to show request and response headers, as well as other debug info.
+If you're using `curl` then you can use the verbose option to show request and response headers, as well as other debug info.
 
 ```shell
 ➜  ~ curl --verbose https://gitlab.example.com/api/v4/projects
@@ -122,5 +122,5 @@ If you have done some horizontal scaling in your GitLab infrastructure, then
 you will need to search across _all_ of your GitLab nodes. You can do this with
 some sort of log aggregation software like Loki, ELK, Splunk, or others.
 
-You can use a tool like Ansible or PSSH (parellel SSH) that can execute commands across your servers in
-parallel to execute the same search command. Or you could craft your own solution.
+You can use a tool like Ansible or PSSH (parellel SSH) that can execute identical commands across your servers in
+parallel, or craft your own solution.