tidy up more 404, redirects, real urls etc

content/en/building/guides/messaging/gateways/africas-talking.md

@@ -22,7 +22,7 @@ As of v3.6.0, SMS messages can be sent and received using the [Africa's Talking]
 
 First generate a long unique key to use as the `cht-api-key`.
 
-Log on to the [Africa's Talking Dashboard](https://account.africastalking.com) and configure your callback URLs as follows.
+Log on to the [Africa's Talking Dashboard](https://account.africastalking.com/auth/login) and configure your callback URLs as follows.
 
 - Delivery Reports: `https://<hostname>/api/v1/sms/africastalking/delivery-reports?key=<cht-api-key>`
 - Incoming Messages: `https://<hostname>/api/v1/sms/africastalking/incoming-messages?key=<cht-api-key>`

content/en/contribute/code/style-guide.md

@@ -51,7 +51,7 @@ a core value of our community. Consider the points of [the opposition][], but
 be a traditionalist when it comes to abusing error correction mechanisms for
 cheap syntactic pleasures.
 
-[the opposition]: http://blog.izs.me/post/2353458699/an-open-letter-to-javascript-leaders-regarding
+[the opposition]: [the opposition]: http://blog.izs.me/post/2353458699/an-open-letter-to-javascript-leaders-regarding
 [hnsemicolons]: http://news.ycombinator.com/item?id=1547647
 
 ### Use single quotes

content/en/contribute/medic/product-development-process/ux-research-repo/_index.md

@@ -6,7 +6,7 @@ description: >
   How to keep track of product research
 ---
 
-The Medic Product team uses [baserow.io](http://baserow.io) as a place to keep product research. Baserow is very similar to [airtable.com](http://airtable.com), [getgrist.com](http://getgrist.com), and Google Sheets.
+The Medic Product team uses [baserow.io](http://baserow.io) as a place to keep product research. Baserow is very similar to [airtable.com](https://www.airtable.com/), [getgrist.com](http://getgrist.com), and Google Sheets.
 
 The _UX Research Repository_ is based off of concepts from WeWork’s [Polaris](https://tsharon.medium.com/democratizing-ux-670b95fbc07f) project. You can see an example of the Polaris (which uses Airtable) [here](https://www.airtable.com/universe/expShuhNMi0Oc0xpb/polaris-ux-nuggets).
 

content/en/contribute/technical-resources.md

@@ -22,7 +22,7 @@ There is a Slack channel in the Medic Workspace called *#cht-dev-workshop* for C
 | **CHT Local Environment and Docs** | [Set up your local development environment]({{% ref "dev-environment" %}}) <br> [Go through CHT Documentation]({{% ref "/" %}}) <br> [Get familiar with the Development Workflow]({{% ref "/contribute/code/workflow" %}}) <br>[Architecture of CHT Instances]({{% ref "architecture" %}}) <br> [CHT Academy - Introduction to Building CHT Application](https://academy.communityhealthtoolkit.org/courses/course-v1:cht-academy+201+2022/about) <br>  [Where to ask questions about the CHT?](https://forum.communityhealthtoolkit.org/) |
 | **JavaScript** | [Eloquent JavaScript](https://eloquentjavascript.net/) <br> [Asynchronous JavaScript Requests](https://www.udacity.com/course/asynchronous-javascript-requests--ud109) <br> [You Don't Know JS](https://github.com/getify/You-Dont-Know-JS) |
 | **TypeScript** | [TypeScript Documentation](https://www.typescriptlang.org/docs/) |
-| **Docker** | [Containers and Docker Mega Thread](https://twitter.com/iximiuz/status/1423984739514454033?s=21) <br> [Docker mastery course](https://www.udemy.com/course/docker-mastery/) <br> [Learn Docker in a month of lunches](https://diamol.net/) <br> [The Ultimate Docker course](https://codewithmosh.com/p/the-ultimate-docker-course) |
+| **Docker** | [Containers and Docker Mega Thread](https://unrollnow.com/status/1423984739514454033) <br> [Docker mastery course](https://www.udemy.com/course/docker-mastery/) <br> [Learn Docker in a month of lunches](https://diamol.net/) <br> [The Ultimate Docker course](https://codewithmosh.com/p/the-ultimate-docker-course) |
 | **Kubernetes** | [Kubernetes documentation](https://kubernetes.io/docs/home/) <br> [Using Kubernetes as a Developer](https://www.pluralsight.com/paths/using-kubernetes-as-a-developer) <br> [Packaging Applications with Helm for Kubernetes](https://www.pluralsight.com/courses/kubernetes-packaging-applications-helm) |
 | **CouchDB and PouchDB** | [CouchDB introduction user guide docs](https://docs.couchdb.org/en/stable/intro/index.html) <br> [Understanding CouchDB 3](https://www.udemy.com/course/understanding-couchdb/) <br> [Introduction to PouchDB](https://pouchdb.com/guides/) |
 | **NodeJS and NPM** | [The Complete Node.JS developer course](https://www.udemy.com/course/the-complete-nodejs-developer-course-2/) <br> [Understanding NPM - Node.js Package Manager](https://www.udemy.com/course/understanding-npm/)|

content/en/core/releases/2.13.0.md

@@ -9,8 +9,8 @@ toc_hide: true
 
 ## Migration notes
 
-- [#2635](https://github.com/medic/cht-core/issues/2635) changes the context available to the configured contact summary script. The `contact` parameter no longer has information about parents. This information is now in an array called `lineage`. More information is available in the [configuration documentation](building/contact-summary/contact-summary-overview/).
-- [#3546](https://github.com/medic/cht-core/issues/3546) changes the implementation of the `contact_summary` so instead of declaring the output on the last line of the script, now you have to return the output. Usually this is as easy as adding a return on the last line, so `output;` becomes `return output;`. More information is available in the [configuration documentation](https://docs.communityhealthtoolkit.org/apps/reference/contact-page/#contact-summary).
+- [#2635](https://github.com/medic/cht-core/issues/2635) changes the context available to the configured contact summary script. The `contact` parameter no longer has information about parents. This information is now in an array called `lineage`. More information is available in the [configuration documentation]( {{< relref "building/contact-summary/contact-summary-overview" >}} ).
+- [#3546](https://github.com/medic/cht-core/issues/3546) changes the implementation of the `contact_summary` so instead of declaring the output on the last line of the script, now you have to return the output. Usually this is as easy as adding a return on the last line, so `output;` becomes `return output;`. More information is available in the [configuration documentation]( {{< relref "building/contact-summary/contact-summary-overview" >}} ).
 
 ## Features
 

content/en/core/releases/2.16.0.md

@@ -210,7 +210,7 @@ We've updated the header when you're viewing reports in the Reports page. The ne
 
 _Because the only thing worse than getting your birthday wrong is…_
 
-In 2.15.0, [we added support for death reporting workflows](./2.15.0.md#death-reporting). One glitch we realized was that the date of death was being set to the date that the death confirmation form was submitted. With 2.16.0, we've added an improvement to the workflow. It's now possible to set a specific date of death in your death confirmation form. This makes the workflow more flexible by allowing a nurse to enter the confirmed date of death in the death confirmation form.
+In 2.15.0, [we added support for death reporting workflows]( {{< relref "core/releases/2.15.0.md#death-reporting" >}} ). One glitch we realized was that the date of death was being set to the date that the death confirmation form was submitted. With 2.16.0, we've added an improvement to the workflow. It's now possible to set a specific date of death in your death confirmation form. This makes the workflow more flexible by allowing a nurse to enter the confirmed date of death in the death confirmation form.
 
 In order to include a user-selected date of death as the official date of death listed in the Medic app, you'll need to make sure there is a field in the death confirmation form that lists the exact date of death and then indicate in your `app_settings` that this field should be used for the date of death.
 

content/en/core/releases/3.10.0.md

@@ -57,7 +57,7 @@ App builders can now configure privacy policies for every language. When a priva
 
 ![privacy policies](../images/3.10-privacy-policies.png)
 
-See [the documentation](https://docs.communityhealthtoolkit.org/apps/guides/security/privacy-policy/) for more information.
+See [the documentation]( {{< relref "building/guides/privacy/privacy-policy" >}} ) for more information.
 
 ## More granular replication depth configuration for offline users
 

content/en/core/releases/3.11.0.md

@@ -83,7 +83,7 @@ The UI framework has been upgraded from the deprecated AngularJS v1.6 to Angular
 
 ### RapidPro SMS gateway
 
-SMS messages can now be sent and received using a RapidPro instance. This allows for integration with a wide range of SMS aggregators for a high scale SMS deployment. Learn more in the [feature documentation](https://docs.communityhealthtoolkit.org/apps/guides/messaging/rapidpro).
+SMS messages can now be sent and received using a RapidPro instance. This allows for integration with a wide range of SMS aggregators for a high scale SMS deployment. Learn more in the [feature documentation]({{< relref "building/guides/messaging/gateways/rapidpro" >}}  ).
 
 - [cht-core#6532](https://github.com/medic/cht-core/issues/6532): Add RapidPro as an SMS Gateway
 

content/en/core/releases/3.4.0.md

@@ -43,7 +43,7 @@ This change removes the continuous replication in favor of making a short lived
 
 ## Customizable branding
 
-You can now configure the webapp logo, title, and favicon to use your project's branding [medic#4849](https://github.com/medic/cht-core/issues/4849). You can also add logos of your partners to show on the About page [medic#4850](https://github.com/medic/cht-core/issues/4850). More information is available in the [feature overview](https://github.com/medic/medic-docs/blob/master/features/webapp-branding.pdf) and the [configuration documentation](https://docs.communityhealthtoolkit.org/apps/reference/resources/).
+You can now configure the webapp logo, title, and favicon to use your project's branding [medic#4849](https://github.com/medic/cht-core/issues/4849). You can also add logos of your partners to show on the About page [medic#4850](https://github.com/medic/cht-core/issues/4850). More information is available in the [feature overview]( {{< relref "building/tutorials/application-graphics" >}} ) and the [configuration documentation](https://docs.communityhealthtoolkit.org/apps/reference/resources/).
 
 ## Improved performance loading Contacts tab
 

content/en/core/releases/3.8.0.md

@@ -115,7 +115,7 @@ These trade-offs are complex and we'd love to hear how these changes affect your
 - [medic-docs#142](https://github.com/medic/medic-docs/issues/142): Accessing and interpreting client-side telemetry
 - [medic-docs#150](https://github.com/medic/medic-docs/issues/150): Add information about the `known` field in documentation
 - [medic-gateway#137](https://github.com/medic/cht-gateway/issues/137): Make sure that Gateway consumes / forwards all SMS before resuming polling
-- [medic-nootils#9](https://github.com/medic/medic-nootils/issues/9): Upgrading to [email protected] includes test-only dependencies
+- [medic-nootils#9](https://github.com/medic/cht-nootils/issues/9): Upgrading to [email protected] includes test-only dependencies
 - [rdt-capture#32](https://github.com/medic/rdt-capture/issues/32): Must target Android 9.0 (API level 28) or above by November 1 2019
 
 ### Performance fixes