Fix named anchor 5/N #260

content/en/apps/guides/forms/app-form-sms.md

@@ -38,7 +38,7 @@ Note that the SMS link notation can be interpreted differently from one phone to
 To define that an XForm should be converted to an SMS, add the field `xml2sms` to the form's CouchDB doc and assign it a truthy value (either a boolean or a string).  
 When submitting such a form, along with creating the report document, the app will try to compact the report's content into an SMS that would be sent to the configured Gateway phone number.
 
-There are two formats available - either using the [ODK's compact record representation for SMS](https://opendatakit.github.io/xforms-spec/#compact-record-representation-(for-sms)), or Medic's custom format.
+There are two formats available - either using the [ODK's compact record representation for SMS](https://getodk.github.io/xforms-spec/#compact-record-representation-(for-sms)), or Medic's custom format.
 When the form compaction fails or returns no content, no SMS will be sent.
 
 ### ODK compact record representation for SMS

content/en/apps/guides/forms/multimedia.md

@@ -15,7 +15,7 @@ relatedContent: >
 
 There are many supported formats for video, audio, and images. We recommend using h.264(mpeg) for video, jpeg for images, and mp3 for audio. When creating videos or images keep in mind the dimensions and storage capabilities on phones that may be used. Lower end phones have smaller storage and screen sizes. When rendering images, video, and audio the CHT uses the browser's built in rendering tools. This means you can render any media format that is supported by the [minimum version of Chrome]({{< ref "core/overview/supported-software#dependencies" >}}).
 
- **List of Supported formats** [video/audio](https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats#Browser_compatibility)
+ **List of Supported formats** [video/audio](https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats)
  [images](https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types)
 
 

content/en/apps/guides/messaging/sms-states.md

@@ -28,7 +28,7 @@ The aggregator also reports on the status of the messages it's sending.
 Both webapp and the aggregator store states/statuses of the messages to keep track of the exchange. They each have their set of statuses, which sometimes are called the same but do not mean the same thing. Watch out.
 
 ### Message statuses in medic-gateway
-See [https://github.com/medic/medic-gateway#content](https://github.com/medic/medic-gateway#content)
+See [https://github.com/medic/medic-gateway#content](https://github.com/medic/medic-gateway#user-content-content)
 
 ### Message states in medic
 

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

@@ -114,7 +114,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]({{< 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 |
+| `icon` | Icon associated with the form. The value is the image's key in the `resources.json` file, as described in the [Icons section]({{< relref "apps/reference/resources#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 |
 | `context.person` | Boolean determining if the form can be seen in the Action list for a person's profile. This is still subject to the `expression`. | no |