diff --git a/content/en/building/guides/interoperability/cht-config.md b/content/en/building/guides/interoperability/cht-config.md
index ba03930cf..d40ad42b0 100644
--- a/content/en/building/guides/interoperability/cht-config.md
+++ b/content/en/building/guides/interoperability/cht-config.md
@@ -1,7 +1,7 @@
 ---
 title: "Configuring CHT applications for interoperability workflows"
-linkTitle: "Configuring CHT applications for interoperability workflows"
-weight:
+linkTitle: "Configuring"
+weight: 1
 description: >
    Guide to setting up forms and outbound push for interoperability
 keywords: interoperability fhir integrations openmrs
diff --git a/content/en/building/guides/interoperability/ltfu.md b/content/en/building/guides/interoperability/ltfu.md
index 1a2032023..1d7d51d84 100644
--- a/content/en/building/guides/interoperability/ltfu.md
+++ b/content/en/building/guides/interoperability/ltfu.md
@@ -1,9 +1,9 @@
 ---
-title: "LTFU reference workflow"
-linkTitle: "LTFU reference workflow"
-weight:
+title: "Loss To Follow-Up reference workflow"
+linkTitle: "Loss To Follow-Up"
+weight: 3
 description: >
-   Guide to testing the LTFU reference workflow
+   Guide to testing the Loss to Follow-Up (LTFU) reference workflow
 keywords: openmrs interoperability
 relatedContent: >
   building/guides/interoperability/cht-config
@@ -12,11 +12,11 @@ relatedContent: >
 
 ## Workflow Testing
 
-This document outlines the steps for testing the Loss To Follow-Up (LTFU) workflow, in addition to documenting the various endpoints available on the mediator. It provides a comprehensive guide on navigating the LTFU workflow and utilizing the endpoints to facilitate the necessary actions.
+This section outlines the steps for testing the Loss To Follow-Up (LTFU) workflow, in addition to documenting the various endpoints available on the mediator. It provides a comprehensive guide on navigating the LTFU workflow and utilizing the endpoints to facilitate the necessary actions.
 
 ## Environments
 
-The document provided includes placeholders for URLs. Replacing these placeholders with the appropriate endpoints for your specific environment is essential to utilize the document correctly. Below are the endpoints provided for each available environment. It is important to note that if your setup differs from the documentation provided, you may need to use different endpoints. By ensuring that the correct endpoints are used, you can be confident in successfully implementing and utilizing the LTFU workflow.
+The section includes placeholders for URLs. Replacing these placeholders with the appropriate endpoints for your specific environment is essential to utilize the guide correctly. Below are the endpoints provided for each available environment. It is important to note that if your setup differs from the documentation provided, you may need to use different endpoints. By ensuring that the correct endpoints are used, you can be confident in successfully implementing and utilizing the LTFU workflow.
 
 ### Docker - Local Setup
 
diff --git a/content/en/building/guides/interoperability/openhim.md b/content/en/building/guides/interoperability/openhim.md
index 6f717fd0c..b5e7c57a0 100644
--- a/content/en/building/guides/interoperability/openhim.md
+++ b/content/en/building/guides/interoperability/openhim.md
@@ -27,11 +27,11 @@ The structure of documents in the CHT database reflects the configuration of the
 
 ![](flow.png)
 
-This project uses OpenHIM as the middleware component with [Mediators](http://openhim.org/docs/configuration/mediators/) to do the conversion. [Outbound Push]({{< ref "building/reference/app-settings/outbound" >}}) is configured to make a request to the middleware when relevant documents are created or modified in the CHT. A Mediator then creates a FHIR resource which is then routed to OpenHIM. OpenHIM routes the resource to any other configured systems.
+CHT Interoperability uses OpenHIM as the middleware component with [Mediators](http://openhim.org/docs/configuration/mediators/) to do the conversion. [Outbound Push]({{< ref "building/reference/app-settings/outbound" >}}) is configured to make a request to the middleware when relevant documents are created or modified in the CHT. A Mediator then creates a FHIR resource which is then routed to OpenHIM. OpenHIM routes the resource to any other configured systems.
 
 Conversely, to bring data into the CHT, OpenHIM is configured to route the updated resource to the Mediator, which then calls the relevant [CHT APIs]({{< ref "building/reference/api" >}}) to update the document in the CHT database. This will then be replicated to users’ devices as per usual.
 
-See more information on the [CHT interoperability]({{< ref "building/concepts/interoperability" >}}) page on the CHT documentation site.
+See more information on the [CHT interoperability page]({{< ref "building/concepts/interoperability" >}}).
 
 ### Prerequisites
 
diff --git a/content/en/building/guides/interoperability/openmrs.md b/content/en/building/guides/interoperability/openmrs.md
index 2a49899e7..c8a134173 100644
--- a/content/en/building/guides/interoperability/openmrs.md
+++ b/content/en/building/guides/interoperability/openmrs.md
@@ -1,7 +1,7 @@
 ---
 title: "OpenMRS Interoperability"
-linkTitle: "OpenMRS Interoperability"
-weight:
+linkTitle: "OpenMRS"
+weight: 4
 description: >
    Exchange data with systems based on OpenMRS using FHIR APIs
 keywords: openmrs interoperability