Apply suggestions from code review

Co-authored-by: Andra Blaj <[email protected]>

content/en/building/guides/interoperability/openhim.md

@@ -1,7 +1,7 @@
 ---
 title: "OpenHIM Mediators"
 linkTitle: "OpenHIM Mediators"
-weight:
+weight: 2
 description: >
    Guide to running OpenHIM and Mediators with Docker Compose
 keywords: openmrs interoperability
@@ -15,15 +15,15 @@ relatedContent: >
 
 #### Overview
 
-The components and reference information for interoperability used in this project are:
+The components and reference information for interoperability used in CHT Interoperability project are:
 
 - [OpenHIE](https://ohie.org/) defines the architecture for an interoperability layer.
 - [OpenHIM](http://openhim.org/) is a middleware component designed to ease interoperability between systems.
 - [HL7 FHIR](https://www.hl7.org/fhir/index.html) is a messaging format to allow all systems to understand the format of the message.
 
 #### CHT
 
-The structure of documents in the CHT database reflect the configuration of the system, and therefore do not map directly to a FHIR message format. To achieve interoperability Medic used a middleware to convert the CHT data structure into a standardized form so the other systems can read it. Below is the standard data workflow:
+The structure of documents in the CHT database reflects the configuration of the system, and therefore, does not map directly to a FHIR message format. To achieve interoperability, the CHT uses a middleware to convert the CHT data structure into a standardized form so the other systems can read it. Below is the standard data workflow:
 
 ![](flow.png)
 

content/en/building/guides/interoperability/troubleshooting.md

@@ -1,7 +1,7 @@
 ---
 title: "Troubleshooting Interoperability"
-linkTitle: "Troubleshooting Interoperability"
-weight:
+linkTitle: "Troubleshooting"
+weight: 5
 description: >
    Guide to troubleshooting OpenHIM, Mediators, and configurations for interoperability workflows
 keywords: openmrs interoperability