fixing doc broken references

Author: dcinzona

docs/config.md

@@ -86,7 +86,7 @@ Options
     Require at least X percent code coverage across the org following the test run.
     Default: 90
 ```
-
+(add-a-custom-task)=
 ### Add a Custom Task
 
 To define a new task for your project, add the task name under the
@@ -534,7 +534,7 @@ will fetch the most recent production release, or the default branch if
 there are no releases. By specifying `resolution_strategy`, the behavior
 can be changed to match desired dependency resolution behavior, such as
 using beta releases or retrieving feature test packages from a commit
-status. See [](dependency-resolution) for
+status. See [](controlling-github-dependency-resolution) for
 more details about resolution strategies.
 
 ```{note}

docs/cumulusci-flow.md

@@ -295,6 +295,7 @@ child branches. This means that despite
 `feature/large-feature__section1` having two child branches, they would
 not receive automerges until the parent branch tests successfully.
 
+(release-to-future-release-merges)=
 ### Release to (Future) Release Merges
 
 Because release branches are so long-lived, and so much work goes into

docs/data.md

@@ -26,7 +26,7 @@ For example, the 'dev' dataset is for 'dev' orgs, and it is used
 instead of the default dataset if it exists.
 
 You can create a dataset by extracting data from an existing org
-or by authoring a [Snowfakery recipe](Generate-Fake-Data).
+or by authoring a [Snowfakery recipe](#generate-fake-data).
 Extracting from an existing org is easy for use-cases where the
 data already exists or can be readily created in an org. Snowfakery
 is better for cases where either a) you would like to dynamically
@@ -37,7 +37,7 @@ A Snowfakery dataset can consist of a single file with a name like
 `datasets/<datasetname>/<datasetname>.recipe.yml` . For example,
 `datasets/default/default.recipe.yml` or
 `datasets/qa/qa.recipe.yml`. The rest of what you need to know
-about Snowfakery is in the section [Generate Fake Data](Generate-Fake-Data).
+about Snowfakery is in the section [Generate Fake Data](#generate-fake-data).
 
 ### Extracting and Loading Sample Datasets
 
@@ -816,11 +816,13 @@ Extract the data for a dataset from an org and persist it to disk.
 
 `mapping` and either `sql_path` or `database_url` must be supplied.
 
-Example: :
-
+Example: 
+```console
     cci task run extract_dataset -o mapping datasets/qa/mapping.yml -o sql_path datasets/qa/data.sql --org qa
+```
 
-### <a name="data-load-dataset"></a> `load_dataset`
+(data-load-dataset)=
+###  `load_dataset`
 
 Load the data for a dataset into an org. If the storage is a database,
 persist new Salesforce Ids to storage.
@@ -840,9 +842,11 @@ persist new Salesforce Ids to storage.
 
 `mapping` and either `sql_path` or `database_url` must be supplied.
 
-Example: :
+Example: 
 
+```console
     cci task run load_dataset -o mapping datasets/qa/mapping.yml -o sql_path datasets/qa/data.sql --org qa
+```
 
 ### `generate_dataset_mapping`
 
@@ -908,9 +912,11 @@ after their target records become available.
 -   `namespace_prefix`: The namespace prefix to treat as belonging to
     the project, if any
 
-Example: :
+Example: 
 
+```console
     cci task run generate_dataset_mapping --org qa -o namespace_prefix my_ns
+```
 
 ### `load_custom_settings`
 
@@ -994,6 +1000,8 @@ option:
 
 You can learn more about Snowfakery syntax in the next section.
 
+(Generate-Fake-Data)=
+
 ## Generate Fake Data
 
 It is possible to use CumulusCI to generate arbitrary amounts of

docs/dev.md

@@ -61,8 +61,7 @@ The [](retrieve-changes) task supports both
 Salesforce DX and Metadata API-format source code. It utilizes the
 [SourceMember](https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_sourcemember.htm)
 `sObject` to detect what has changed in an org, and also gives you
-discretion regarding which components are retrieved when compared to the
-[](dx-pull) task.
+discretion regarding which components are retrieved.
 
 To retrieve _all_ changes in an org:
 
@@ -161,14 +160,7 @@ code and metadata stored in the repository. After making changes in an
 editor, push these changes from your project's local repository to the
 target org.
 
-If your project uses the Salesforce DX source format, use the
-[](dx-push) task.
-
-```console
-$ cci task run dx_push
-```
-
-If your project uses the Metadata API source format, use the
+To push your changes, use the
 [](deploy) task:
 
 ```console

docs/env-var-reference.md

@@ -26,6 +26,7 @@ OS keychain is not available.
 Used for specifying a GitHub Repository for CumulusCI to use when
 running in a CI environment.
 
+(cumulusci-system-certs)=
 ## `CUMULUSCI_SYSTEM_CERTS`
 
 If set to `True`, CumulusCI will configure the Python `requests` library
@@ -42,6 +43,7 @@ Your GitHub App's identifier.
 Contents of a JSON Web Token (JWT) used to [authenticate a GitHub
 app](https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/##authenticating-as-a-github-app).
 
+(github-token)=
 ## `GITHUB_TOKEN`
 
 A GitHub [personal access

docs/get-started.md

@@ -122,6 +122,7 @@ pipx install cumulusci
 
 When finished, [verify your installation](verify-your-installation).
 
+(update-environment-variables-manually)=
 #### Update Environment Variables Manually
 
 1.  Click Start and search for `edit environment variables`, or open

docs/headless.md

@@ -86,7 +86,7 @@ then the attributes: `callback_url`, `client_id`, and `client_secret`
 would need to be provided in the following format:
 
 ```json
-"{"callback_url": "<callback_url>", "client_id": "<client_id>", "client_secret": "<client_secret>"}"
+{"callback_url": "<callback_url>", "client_id": "<client_id>", "client_secret": "<client_secret>"}
 ```
 
 > The values `<callback_url>`, `<client_id>`, and `<client_secret>`