Fix named anchor 2/N #260

content/en/apps/guides/database/rdbms-from-windows.md

@@ -19,7 +19,7 @@ Connecting to RDBMS, the PostgreSQL server, is pretty stratightforward in nix sy
 
 ![Putty-gen-key-pair](puttygen-run-key-generate.png)
 
-4. Convert the key generated from ssh2 format to openssh. Puttygen supports this. Guide [here](https://stackoverflow.com/questions/2224066/how-to-convert-ssh-keypairs-generated-using-puttygenwindows-into-key-pairs-use?answertab=votes#tab-top)
+4. Convert the key generated from ssh2 format to openssh. Puttygen [supports this](https://stackoverflow.com/a/2224204).
 
 ```
 1. Open PuttyGen

content/en/apps/guides/hosting/ec2-setup-guide.md

@@ -62,7 +62,7 @@ sudo chmod 0600 ~/Downloads/name_of_file.pem
 ## Troubleshooting
 #### 1. Restarting processes
 - [How to access container, retrieve logs, isolate security groups]({{< ref "apps/guides/hosting/self-hosting#how-to-access-container-retrieve-logs-isolate-security-groups" >}})
-- [MedicOS service management scripts](https://github.com/medic/medic-os#service-management-scripts)
+- [MedicOS service management scripts](https://github.com/medic/medic-os#user-content-service-management-scripts)
 
 #### 2. Investigating logs
 - [Log into container](https://docs.docker.com/engine/reference/commandline/exec/)

content/en/apps/guides/hosting/self-hosting.md

@@ -11,8 +11,7 @@ relatedContent: >
  ## Self Hosting
 
 ### How to access container, retrieve logs, isolate security groups
-* How to restart services: Link to medic-os documentation
-https://github.com/medic/medic-os#service-management-scripts
+* How to [restart services](https://github.com/medic/medic-os#user-content-service-management-scripts):
 `/boot/svc-<start/stop/restart> <service-name/medic-api/medic-sentinel/medic-core couchdb/medic-core nginx>`
 
 ### AWS docs for increasing disk size:

content/en/apps/reference/forms/app.md

@@ -25,7 +25,7 @@ A CHT-enhanced version of the ODK XForm standard is supported.
 
 Data needed during the completion of the form (eg patient's name, prior information) is passed into the `inputs` group. Reports that have at least one of `place_id`, `patient_id`, and `patient_uuid` at the top level will be associated with that contact. 
 
-{{< see-also page="apps/reference/forms/contact" anchor="care-guides" title="Passing contact data to care guides" >}}
+{{< see-also page="apps/reference/forms/contact" title="Passing contact data to care guides" >}}
 
 A typical form ends with a summary group (eg `group_summary`, or `group_review`) where important information is shown to the user before they submit the form.
 
@@ -113,7 +113,7 @@ The meta information in the `{form_name}.properties.json` file defines the form'
 
 | property | description | required |
 |---|---|---|
-| `title`| The form's title seen in the app. Uses a localization array using the 2-letter code, not the translation keys discussed in the [Localization section](#localization). | yes |
+| `title`| The form's title seen in the app. Uses a localization array using the 2-letter code, not the translation keys discussed in the [Localization section]({{< relref "apps/reference/translations" >}}). | yes |
 | `icon` | Icon associated with the form. The value is the image's key in the `resources.json` file, as described in the [Icons section](#icons) | yes |
 | `subject_key` | Override the default report list title with a custom translation key. The translation uses a summary of the report as the evaluation context so you can include report fields in your value, for example: `Case registration {{case_id}}`. Useful properties available in the summary include: `from` (the phone number of the sender), `phone` (the phone number of the report contact), `form` (the form code), `subject.name` (the name of the subject), and `case_id` (the generated case id). Defaults to the name of the report subject. | no |
 | `context` | The context defines when and where the form should be available in the app | no |

content/en/contribute/docs/workflow.md

@@ -15,7 +15,7 @@ Anyone can contribute to CHT documentation by opening an issue in the [`cht-docs
 * It is helpful to be comfortable with [git]({{< ref "core/guides/using-git" >}}) and [GitHub](https://lab.github.com/) to contribute to the CHT community.
 * The documentation source is in [GitHub](https://github.com/medic/cht-docs). The content pages are in the `/content/en/` directory.
 * Documentation is written in [Markdown](https://www.markdownguide.org/). 
-* The CHT site build uses [Hugo](https://gohugo.io/). You can also setup a [local clone](https://github.com/medic/cht-docs/blob/master/README.md#installing-hugo). 
+* The CHT site build uses [Hugo](https://gohugo.io/). You can also setup a [local clone](https://github.com/medic/cht-docs/blob/master/README.md). 
 
 ## Writing Documentation