Fix some broken links in custom DC page (#646)

* Revert to gerund

Though the style guide says to just use imperatives, "get started" just sounds weird. Also this is more consistent with "troubleshooting"

* merge

* merge

* stable release

* removed reference to fork

* updated procedures

* wee corrections

* recorrect

* wee changes

* wee changes

* remove branch sync procedures

* corrections from Hannah

* first revisions

* more revisions

* more work

* first cut of variable-per-column rewrite

* more work

* more work

* more work

* restore changes

* more changes

* more changes

* more changes

* more changes

* updates to json spec

* more edits

* multiple directories

* more changes

* more changes

* more edits

* remove headings from TOC

* minor edits

* more edits

* remove wrong image reference

* remove more headings from TOC

* revisions per Ajai and a new diagram

* remove image, replace by text

* mention that node and field order in MCF do not matter

* added mention of required option for subdirs

* added note about MCF

* move feedback from index page to FAQ

* added info on stat var groups

* wee fixes

* make feedback links nicer

* added detail about measuredProperty in variable per column

* fix typo

* revert output directory change

* fixed observation properties to refer to observations, not variables

* correct erroneous statement about data

* revert change

* Updating Data Sources pages

* Updating Data Sources pages

* added 2 more troubleshooting tips based on CE experience

* revert changes to local client

* make enable subdirs more prominent

* fixed incorrect Docker commands

* slight wording change

* fix formatting error in quickstart

* Fix incorrect field name

* Add more spaces to make more readable

* change groupstatvars to be available for both modes

* Start rewrite of custom DC docs with script

* more script work

* more work

* More work on script

* more work

* More script work

* fix path

* fix broken link to website FAQ

* Fix toc

* Add docker commands underlying bash script

* Split out config reference into separate file

* Add the git clone procedure as a prequisite

* slight rewording

* small wording changes

* Added more caveats to Cloud section

* Add reference to Terraform script

* Add info about prefixes in DCIDs

* Add rules for observation values

* Add link to look up DCID

* Push for real

* feedback from Keyur

* remove references to dataclass objects

* Fix a copy-paste error.

* remove extra file

* addeddoc of Cloud Shell

* Add mention of cloud shell in the cloud page

* Added observationProperties to the implicit schema doc

* update comparison table

* remove errant angle bracket

* changes to config.json

* remove redundant sentence

* Fix broken links

* fix href

* Add a dedicated support page

Author: kmoscoe

custom_dc/deploy_cloud.md

@@ -72,7 +72,7 @@ To run it:
 
 The project ID may be the same project you are using for all other resources, or it may be a separate one you use for pushing releases.
 
-To verify that the repository is created, go to [https://console.cloud.google.com/artifacts](https://console.cloud.google.com/artifacts){target="_blank"} for your project. You should see the repository in the list.
+To verify that the repository is created, go to [https://console.cloud.google.com/artifacts](https://console.cloud.google.com/artifacts){: target="_blank"} for your project. You should see the repository in the list.
 
 ## Configure and run a Terraform deployment {#terraform}
 
@@ -288,11 +288,11 @@ Any time you make changes to the website and want to deploy your changes to the
    <div class="active">
    To upload an already built image:
     <pre>./run_cdc_dev_docker.sh --actions upload --image <var>SOURCE_IMAGE_NAME</var>:<var>SOURCE_IMAGE_TAG</var> [--package <var>TARGET_IMAGE_NAME</var>:<var>TARGET_IMAGE_TAG</var>]</pre>
-   To build and upload the image:
+   To build a new image and and upload it:
    <pre>./run_cdc_dev_docker.sh --actions build_upload --image <var>IMAGE_NAME</var>:<var>IMAGE_TAG</var> [--package <var>TARGET_IMAGE_NAME</var>:<var>TARGET_IMAGE_TAG</var>]</pre>
    If you don't specify the <code>--package</code> option, the package name and tag will be the same as the source image.
    </div>
-    <div><ol><li>Build a local version of the Docker image, following the procedure in <a href="build_image.md#build-repo">Build a local image</a>.</li>
+    <div><ol><li>Build a local version of the Docker image, following the procedure in <a href="/custom_dc/build_image.html#build-repo">Build a local image</a>.</li>
       <li>Generate credentials for the Docker package. 
     <pre>gcloud auth configure-docker <var>REGION</var>-docker.pkg.dev</pre></li>
    <li>Create a package from the source image you created in step 1:

custom_dc/faq.md

@@ -25,11 +25,7 @@ For detailed comparison on the differences between base and custom Data Commons,
 
 ### How can I request new features or provide feedback? {#feedback}
 
-We use [Google Issue Tracker](https://issuetracker.google.com){: target="_blank"} to track bugs and feature requests. All tickets are publicly viewable.
-
-Before opening a new ticket, please see if an existing [feature request](https://issuetracker.google.com/issues?q=componentid:1659535%2B%20type:feature_request){: target="_blank"} or [bug report](https://issuetracker.google.com/issues?q=componentid:1659535%20type:bug){: target="_blank"} covering your issue has already been filed. If yes, upvote (click the **+1** button ) and [subscribe](https://developers.google.com/issue-tracker/guides/subscribe){: target="_blank"} to it. If not, open a new [feature request](https://issuetracker.google.com/issues/new?component=1659535&template=2053233){: target="_blank"} or [bug report](https://issuetracker.google.com/issues/new?component=1659535&template=2053231){: target="_blank"}.
-
-For any issue you file, make sure to indicate that it affects your Data Commons instance.
+Please see [Get support](support.md).
 
 ## Privacy and security
 

support.md

@@ -0,0 +1,28 @@
+---
+layout: default
+title: Get support
+nav_order: 6
+parent: How to use Data Commons
+---
+
+{: .no_toc}
+# Get support
+
+* TOC
+{:toc}
+
+## Check the FAQ
+
+The [datacommons.org website](https://datacommons.org/faq){: target="_blank"} provides answers to common questions. Check here first!
+
+## File a bug or feature request
+
+We use [Google Issue Tracker](https://issuetracker.google.com){: target="_blank"} to track bugs and feature requests. All tickets are publicly viewable.
+
+Before opening a new ticket, please see if an existing [feature request](https://issuetracker.google.com/issues?q=componentid:1659535%2B%20type:feature_request){: target="_blank"} or [bug report](https://issuetracker.google.com/issues?q=componentid:1659535%20type:bug){: target="_blank"} covering your issue has already been filed. If yes, upvote (click the **+1** button ) and [subscribe](https://developers.google.com/issue-tracker/guides/subscribe){: target="_blank"} to it. If not, open a new [feature request](https://issuetracker.google.com/issues/new?component=1659535&template=2053233){: target="_blank"} or [bug report](https://issuetracker.google.com/issues/new?component=1659535&template=2053231){: target="_blank"}.
+
+If you are using a Custom Data instance, make sure to indicate that the issue affects your instance.
+
+## Email support forum
+
+For technical questions that you can't find answers to in this documentation, you can email [email protected].