Fix: correcting typos (#1411)

* Fix typos

* Undo file name change and treshold fix

---------

Co-authored-by: mariachana_moturi <[email protected]>

content/en/apps/examples/direct-to-client.md

@@ -102,7 +102,7 @@ If the client has not responded to any of the daily check in-messages by day 3,
 A VMMC client who responds with a potential complication triggers a Client review: Potential complication task for the 2WT nurse. They then report and fill in whether the client was reviewed by a clinician. If the client has been reviewed by a clinician, they record the details of the review, time, place and adverse events identified. If the client has not been reviewed by a clinician, the 2WT nurse will try and trace them by SMS, phone call or a home visit; and report the tracing outcomes as shown in figure 6 below.
 
 
-{{< figure src="Figure6Escalted.png"  link="Figure6Escalted.png" alt="" title="" caption="<b>Figure 6:</b> Direct-to-client messaging for voluntary male circumcision clients without adverse effects" class="col-9">}}
+{{< figure src="Figure6Escalated.png"  link="Figure6Escalated.png" alt="" title="" caption="<b>Figure 6:</b> Direct-to-client messaging for voluntary male circumcision clients without adverse effects" class="col-9">}}
 
 
 #### 4. Clients can share requests by messaging health care providers.

content/en/apps/examples/interoperability.md

@@ -13,7 +13,7 @@ This workflow describes a use case where a health facility or a requesting syste
 
 ## Problem Being Addressed
 
-Data exchange between the CHT and other systems has primarily been at peer-to-peer level. This means that the integration is built to meet the specific need in the unique scenarios. This presents a problem during maintainance and scalability as there are no defined standards that have been used. [Interoperability](https://docs.communityhealthtoolkit.org/apps/concepts/interoperability/) allows technical teams to scale in an efficient and repeatable manner due to the already predefined standards. 
+Data exchange between the CHT and other systems has primarily been at peer-to-peer level. This means that the integration is built to meet the specific need in the unique scenarios. This presents a problem during maintenance and scalability as there are no defined standards that have been used. [Interoperability](https://docs.communityhealthtoolkit.org/apps/concepts/interoperability/) allows technical teams to scale in an efficient and repeatable manner due to the already predefined standards. 
 
 
 ## Solution Overview

content/en/apps/examples/phc-covid.md

@@ -33,7 +33,7 @@ Through adaptations to PHC workflows, health program administrators are able to:
 * Support COVID-19 prevention, detection, and containment efforts within communities
 * Create a coordinated approach that safely serves health workers, facilities, and communities 
 * Support home-based care for non-emergent COVID-19 cases to reduce overburdening on hospital systems
-* Capture program learnings to create more robust and resilient health systems beyond supporting the immediate COVID-19 reponse
+* Capture program learnings to create more robust and resilient health systems beyond supporting the immediate COVID-19 response
 
 ## Users and Hierarchy Example
 

content/en/apps/examples/pih.md

@@ -53,7 +53,7 @@ This workflow consists of the pregnancy, delivery and postnatal workflows.The pr
         resolution="The woman visits the health facility, gets a pregnancy test and starts ANC clinic."
   %}}
   {{% workflow
-        condition="Incase of a confirmed pregnancy(woman has started ANC visits) the CHW submits a **Pregnancy Registration Form** with gestational age and facility EDD if available."
+        condition="In case of a confirmed pregnancy(woman has started ANC visits) the CHW submits a **Pregnancy Registration Form** with gestational age and facility EDD if available."
         task="Every first day of the month, the CHW receives **Pregnancy Follow-Up Task** to remind that it is time to check into pregnant mother. The tasks continue for 42 weeks."
         resolution="The CHW submits **Pregnancy Follow-Up Form** demonstrating that she provided ANC counseling, gathered information from prior facility visits, screened for danger signs and reminded the woman of her upcoming facility ANC visit."
   %}}

content/en/apps/guides/android/branding.md

@@ -63,7 +63,7 @@ If you are going to publish the app in the **Play Store**, Google will require t
 - A background image.
 - Screenshots.
 
-Google is constantly changing the requirments to publish in the Play Store, it's a good practice to check in advance whether all the requirements are met (checkout _[Add preview assets...](https://support.google.com/googleplay/android-developer/answer/9866151)_).
+Google is constantly changing the requirements to publish in the Play Store, it's a good practice to check in advance whether all the requirements are met (checkout _[Add preview assets...](https://support.google.com/googleplay/android-developer/answer/9866151)_).
 
 ##### Test data
 

content/en/apps/guides/data/csv-to-docs.md

@@ -163,7 +163,7 @@ For instance, to include the parent district's doc in a health center's doc, the
 
 ##### Including value from another doc
 
-Similar to including another doc, it is also possible to get the value of a specific field in another doc. For instance, if `parent:GET _id OF place WHERE reference_id=COL_VAL` were used in the example above, the `parent` field's value would have been set to the `_id` of the refered to doc instead of including the whole doc. Note that `_id` is a generated value included in all generated docs.
+Similar to including another doc, it is also possible to get the value of a specific field in another doc. For instance, if `parent:GET _id OF place WHERE reference_id=COL_VAL` were used in the example above, the `parent` field's value would have been set to the `_id` of the referred to doc instead of including the whole doc. Note that `_id` is a generated value included in all generated docs.
 
 | reference_id:excluded | parent:GET _id OF place WHERE reference_id=COL_VAL | is_name_generated | name | reported_date:timestamp |
 | --------------------- | -------------------------------------------------- | ----------------- | ---- | ----------------------- |

content/en/apps/guides/data/users-bulk-load.md

@@ -209,7 +209,7 @@ If a user you successfully created can not log in because they see an error:
 
 ![Access denied - You have insufficient privileges to view this page. Talk to an administrator to increase your privileges](access.denied.png)
 
-A possible cause of this is you have a bad role defined in your spreadsheet that doesn't match your configuration.  For example, the the default role should be `chw_supervisor`, but here we see garbage characters were accidentally added.  While the user was created without errors, they'll see the above error when they try to log in:
+A possible cause of this is you have a bad role defined in your spreadsheet that doesn't match your configuration. For example, the the default role should be `chw_supervisor`, but here we see garbage characters were accidentally added.  While the user was created without errors, they'll see the above error when they try to log in:
 
 ![Bad type declared in spreadsheet causes the user to have no role](bad.type.png)
 

content/en/apps/guides/integrations/dhis2-aggregate.md

@@ -27,7 +27,7 @@ These considerations are summarized below.
 The CHT relies on your Place hierarchy to determine how data should be aggregated for DHIS2. As such, it’s important that you consider how organization units are configured in the DHIS2 instance that you need to integrate data into. If your CHT Place hierarchy does not align with the DHIS2 organisation unit structure, the CHT will not be able to aggregate data in the way DHIS2 needs it.
 
 {{% alert title="Note" %}}
-There should be a one-to-one relationship between DHIS2 organistion units and CHT places.
+There should be a one-to-one relationship between DHIS2 organisation units and CHT places.
 {{% /alert %}}
 
 

content/en/apps/guides/integrations/openmrs.md

@@ -56,7 +56,7 @@ Here, you need to capture the basic details required for registering a patient o
 `patient_firstName` for first_name,
 `patient_middleName` for middle_name
 
-Another example of patient identifiers could take the form `_IdentiferType_humanReadableName_IdentifierTypeUuid`. For example, national Id identifier type definition would be, `patient_identifierType_nationalId_49af6cdc-7968-4abb-bf46-de10d7f4859f`.
+Another example of patient identifiers could take the form `_IdentifierType_humanReadableName_IdentifierTypeUuid`. For example, national Id identifier type definition would be, `patient_identifierType_nationalId_49af6cdc-7968-4abb-bf46-de10d7f4859f`.
 
 A sample form definition could be as follows:
 
@@ -115,7 +115,7 @@ Here is a sample form snippet followed by sample select list in the choices work
 | begin group                   | group_assessment  | Assessment                         |          |                     |            |            |                     |             |                |      |         |
 | select_one client_consented             | _1710_clientConsented_99DCT             | Has ${patient_name} consented? | yes      |                     |            |            |                     |             |                |      |         |
 | select_multiple disability_type   | _162558_disabilityTypeMULTISELECT_99DCT    | Disability type     | yes      |     |            |            |                     |             |                |      |         |
-| text   | _160632_Specify_99DCT    | Specify (0ther)     | yes      | ${_162558_disabilityTypeMULTISELECT_99DCT} = 'other'    |            |            |                     |             |                |      |         |
+| text   | _160632_Specify_99DCT    | Specify (Other)     | yes      | ${_162558_disabilityTypeMULTISELECT_99DCT} = 'other'    |            |            |                     |             |                |      |         |
 | end group                     |                   |                                    |          |                     |            |            |                     |             |                |      |         |
 
 ##### Choices
@@ -169,7 +169,7 @@ First, the data has to be transformed to an OpenMRS-compatible format before it
       "1542^OCCUPATION^99DCT": "1538^Farmer^99DCT"
     },
     "discriminator": {
-      "dicriminator": "registration"
+      "discriminator": "registration"
     }
 }
 ```

content/en/apps/guides/integrations/rapidpro.md

@@ -52,7 +52,7 @@ Before designing your integrated RapidPro/CHT workflow, it's important to unders
 
 ## Workflow Design
 
-Designing an integrated workflow between mutliple systems is more of an art than a science. Drafting a sequence diagram (below) is a good first step. When drafting your sequence diagram, it is useful to consider a few key integration touchpoints that are common across many integrated workflows.
+Designing an integrated workflow between multiple systems is more of an art than a science. Drafting a sequence diagram (below) is a good first step. When drafting your sequence diagram, it is useful to consider a few key integration touchpoints that are common across many integrated workflows.
 
 1. One system **initiates or triggers an action in** the other system
 2. One system needs to **get information from** the other system

content/en/apps/guides/messaging/gateways/gateway/phones.md

@@ -11,7 +11,7 @@ relatedContent: >
   apps/guides/messaging/gateways/gateway/configuration
 ---
 
-In order to use SMS workflows with the CHT you will need an SMS gateway. For reliability an SMS Aggregator, such as [Africa's Talking]({{< ref "apps/guides/messaging/gateways/africas-talking" >}}) or [RapidPro]({{< ref "apps/guides/messaging/gateways/rapidpro" >}}), is recommended. When an SMS Aggregator is not available, an Android device running [CHT Gateway](https://github.com/medic/cht-gateway) can be used to send and receive SMS in your CHT appplication. You may use an existing Android device and are not required to purchase a new one. However, for more reliable sending and receiving of SMS, the Android device should be in your organization’s office or facility with a consistent internet connection.
+In order to use SMS workflows with the CHT you will need an SMS gateway. For reliability an SMS Aggregator, such as [Africa's Talking]({{< ref "apps/guides/messaging/gateways/africas-talking" >}}) or [RapidPro]({{< ref "apps/guides/messaging/gateways/rapidpro" >}}), is recommended. When an SMS Aggregator is not available, an Android device running [CHT Gateway](https://github.com/medic/cht-gateway) can be used to send and receive SMS in your CHT application. You may use an existing Android device and are not required to purchase a new one. However, for more reliable sending and receiving of SMS, the Android device should be in your organization’s office or facility with a consistent internet connection.
 
 Below is a list of recommended Android devices across a range of prices. You may find these in local mobile equipment stores as well as online through Amazon and other e-commerce sites. 
 

content/en/apps/guides/messaging/gateways/gateway/troubleshooting.md

@@ -11,7 +11,7 @@ relatedContent: >
   apps/guides/messaging/gateways/gateway/configuration
 ---
 
-In a techlead heaven, we would have immeadiate physical access to gateway phones, but alas, most of the time we have to hand them over to the partner. Fortunately, comes this guide on debugging gateway problems.
+In a techlead heaven, we would have immediate physical access to gateway phones, but alas, most of the time we have to hand them over to the partner. Fortunately, comes this guide on debugging gateway problems.
 
 Follow the steps as below (if you don't have physical access to the phone, start with step 2 i.e debug from the server side first)
 
@@ -22,9 +22,9 @@ Follow the steps as below (if you don't have physical access to the phone, start
 
         ![Settings Screen](settings_screen.png)
 
-	3. Has the latest Gateway version. Get the latest version by opening the Google Playstore, searching for `Medic Gateway` and updating the existing app
+	3. Has the latest Gateway version. Get the latest version by opening the Google Play Store, searching for `Medic Gateway` and updating the existing app
 
-	4. Medic Gatway should be set as the default app for SMS. To check, go to `Settings` in the Gateway app. If Medic Gateway is not the default, you will be met with the below app screen. In that case, click `Help me change`.
+	4. Medic Gateway should be set as the default app for SMS. To check, go to `Settings` in the Gateway app. If Medic Gateway is not the default, you will be met with the below app screen. In that case, click `Help me change`.
 
         ![Not Default](not_default.png)
 
@@ -36,7 +36,7 @@ Follow the steps as below (if you don't have physical access to the phone, start
 
 	8. Check if the phone has adequate free space
 
-	9. Restart the phone if no solution seems to work. Resetting the Adroind state sometimes resolves some persistent problems
+	9. Restart the phone if no solution seems to work. Resetting the Android state sometimes resolves some persistent problems
 
 2.  When attacking the problem from the phones end does not work, move on to the server and try to solve it from there. Maybe the server has a configuration issue which hinders the processing or the acceptance of the messages by `Medic-Api`
 Follow the steps:

content/en/apps/guides/performance/purging.md

@@ -106,7 +106,7 @@ This function takes six parameters:
 - `contact`, the contact document of a patient or other contact who has reports about them.
 - `reports`, an array of all reports for that subject that are present on the server.
 - `messages`, an array of sms messages that the contact has sent or received.
-- `chtScriptApi` (Optional) the CHT API that provides CHT-Core Framwework's functions to other parts of the app. More info on the API can be found [here]({{<ref "apps/reference/_partial_cht_api" >}}). Added in 4.3.0.
+- `chtScriptApi` (Optional) the CHT API that provides CHT-Core Framework's functions to other parts of the app. More info on the API can be found [here]({{<ref "apps/reference/_partial_cht_api" >}}). Added in 4.3.0.
 - `permissions` (Optional) string or array of permissions that the user has. More info on permissions can be found [here]({{<ref "apps/reference/app-settings/user-permissions" >}}). Added in 4.3.0.
 
 And should return an array of `_id` values for docs you would like to be purged (or `undefined` / nothing if you don't wish to purge anything). `Only ids of docs that were passed to the function are valid for purging: you are not allowed to purge other documents.

content/en/apps/guides/performance/telemetry.md

@@ -64,8 +64,8 @@ Find below the list of telemetry data recorded by CHT:
 | `search:reports:<filter[:filter]>` | The time taken to search all reports using the given filters. | |
 | `contact_detail:<contact_type>:load` | On the People tab, the time taken to load a contact, from the time the contact was selected to the time all content for that contact (contact summary, condition cards, reports, tasks, etc...) has fully loaded on the screen. Added in 4.7. |  Yes. Added in 4.7|
 | `contact_detail:<_form>:load:contact_data` | The time taken to load a contact's data. Added in 4.7. | | 
-| `contact_detail:<_form>:load:load_descendants` | The time taken to load a contact's descendants, that is places and contacts under the contact heriarchy level. Added in 4.7. | |
-| `contact_detail:<_form>:load:load_reports` |  The time taken to load a contact's asociated reports. Added in 4.7. | |
+| `contact_detail:<_form>:load:load_descendants` | The time taken to load a contact's descendants, that is places and contacts under the contact hierarchy level. Added in 4.7. | |
+| `contact_detail:<_form>:load:load_reports` |  The time taken to load a contact's associated reports. Added in 4.7. | |
 | `contact_detail:<_form>:load:load_targets` |  The time taken to load a contact's targets. Added in 4.7. | |
 | `contact_detail:<_form>:load:load_tasks` |  The time taken to load a contact's tasks. Added in 4.7. | |
 | `contact_detail:<_form>:load:load_contact_summary` |  The time taken to load a contact's contact-summary. Added in 4.7. | |

content/en/apps/guides/security/securely-onboarding-users-at-scale.md

@@ -77,7 +77,7 @@ For deployments that are centrally provisioning devices, it is acceptable for ge
 
 ### Worst practice: Shared list, anonymous access, similar passwords
 
-Create all users with near identical passwords (eg `password123`, `passord234`, `password345` etc.) that are then printed out, shared via email or posted to a public URL which requires no authentication.  Send an SMS to the CHW with username, password and URL of the device.
+Create all users with near identical passwords (eg `password123`, `passord234`, `password345` etc.) that are then printed out, shared via email or posted to a public URL which requires no authentication. Send an SMS to the CHW with username, password and URL of the device.
 
 There's many failures here:
 * Passwords are predictable and easy to guess
@@ -89,7 +89,7 @@ There's many failures here:
 By knowing what the security threats are you can know the most helpful steps to remediate them to limit the damage done to the CHT deployment, the privacy of the patients and the security of CHWs.
 
 {{% alert title="Note" %}}
-Users who have their password changed can continue to use the CHT to deliver care.  They need to _keep their device offline_ though. After a password change, when a CHW attempts to sync, they will be prompted to log in. At that point, they wlll not be able to continue using the CHT until they log in.
+Users who have their password changed can continue to use the CHT to deliver care.  They need to _keep their device offline_ though. After a password change, when a CHW attempts to sync, they will be prompted to log in. At that point, they will not be able to continue using the CHT until they log in.
 No data will be lost if they log in as the _same user_.
 {{% /alert %}}
 

content/en/apps/reference/api.md

@@ -56,7 +56,7 @@ Returns the settings in JSON format.
 
 | Variable | Description                                                                                             |
 | -------- | ------------------------------------------------------------------------------------------------------- |
-| overwrite  | Whether to replace settings document with input document. If both replace and overwite are set, then it overwites only. Defaults to replace. |
+| overwrite  | Whether to replace settings document with input document. If both replace and overwrite are set, then it overwrites only. Defaults to replace. |
 | replace  | Whether to replace existing settings for the given properties or to merge. Defaults to false (merging). |
 
 Returns a JSON object with two fields: