Fix backup and restore API docs bugs

Author: jhlodin

src/current/_includes/cockroachcloud/backups/cloud-api-backup-settings.md

@@ -1,17 +1,17 @@
 ### Get information on backup settings
 
-To retrieve information about a specific cluster, make a `GET` request to the `/v1/clusters/{cluster_id}/backups/config` endpoint.
+To retrieve information about a specific cluster, make a `GET` request to the `/v1/clusters/{cluster_id}/backups-config` endpoint.
 
 {% include_cached copy-clipboard.html %}
 ~~~ shell
 curl --request GET \
---url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/backups/config \
+--url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/backups-config \
 --header 'Authorization: Bearer {secret_key}'
 ~~~
 
 Set the following:
 
-- `{cluster_id}` is the unique ID of the cluster. Use this ID when making API requests. You can find the cluster ID in the cluster's Cloud Console page. Find your cluster ID in the URL of the single cluster overview page: `https://cockroachlabs.cloud/cluster/{your_cluster_id}/overview`. The ID should resemble `f78b7feb-b6cf-4396-9d7f-494982d7d81e`.
+- `{cluster_id}` is the unique ID of the cluster. This ID is written in a UUID format similar to `f78b7feb-b6cf-4396-9d7f-494982d7d81e` and is returned by a [GET request against the `/v1/clusters` endpoint]({% link cockroachcloud/cloud-api.md %}#list-all-clusters-in-an-organization). You can also find the cluster ID in the Cloud Console, in the URL of the single cluster overview page: `https://cockroachlabs.cloud/cluster/{your_cluster_id}/overview`.
 - `{secret_key}` is your API key. Refer to [API Access]({% link cockroachcloud/managing-access.md %}#api-access) for more details.
 
 If the request is successful, the API will return details about the managed backup settings:
@@ -36,19 +36,19 @@ If the request is successful, the API will return details about the managed back
 
 {% include cockroachcloud/backups/review-settings.md %}
 
-To configure the frequency and retention of managed backups, send a `PUT` request to the `/v1/clusters/{cluster_id}/backups/config` endpoint.
+To configure the frequency and retention of managed backups, send a `PUT` request to the `/v1/clusters/{cluster_id}/backups-config` endpoint.
 
 {% include_cached copy-clipboard.html %}
 ~~~ shell
 curl --request PUT \
---url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/backups/config \
+--url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/backups-config \
 --header 'Authorization: Bearer {secret_key}' \
 --data '{"enabled": true, "frequency_minutes": 30, "retention_days": 2}'
 ~~~
 
 Set the following:
 
-- `{cluster_id}` is the unique ID of the cluster. Use this ID when making API requests. You can find the cluster ID in the cluster's Cloud Console page. Find your cluster ID in the URL of the single cluster overview page: `https://cockroachlabs.cloud/cluster/{your_cluster_id}/overview`. The ID should resemble `f78b7feb-b6cf-4396-9d7f-494982d7d81e`.
+- `{cluster_id}` is the unique ID of the cluster. This ID is written in a UUID format similar to `f78b7feb-b6cf-4396-9d7f-494982d7d81e` and is returned by a [GET request against the `/v1/clusters` endpoint]({% link cockroachcloud/cloud-api.md %}#list-all-clusters-in-an-organization). You can also find the cluster ID in the Cloud Console, in the URL of the single cluster overview page: `https://cockroachlabs.cloud/cluster/{your_cluster_id}/overview`.
 - `{enabled}` controls whether managed backups are enabled or disabled. If you are disabling managed backups, you cannot set backup frequency or retention. Possible values are: `true`, `false`.
 - `{frequency_minutes}` determines [how often](#frequency) the managed backup will run in minutes. Possible values are: `5`, `10`, `15`, `30`, `60`, `240` (4 hours), `1440` (24 hours).
 - `{retention_days}` sets the number of days Cockroach Labs will [retain](#retention) the managed backup in storage. You can change `retention_days` for the cluster **once** (whether in the Cloud API or [Cloud Console](#cloud-console)). Possible values are: `2`, `7`, `30`, `90`, `365`.

src/current/_includes/cockroachcloud/backups/cloud-api-restore-endpoint.md

@@ -26,7 +26,7 @@ curl --request POST \
 --url 'https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores' \
 --header "Authorization: Bearer {secret_key}" \
 --json '{
-    "source_cluster_id": "{cluster_id}"
+    "source_cluster_id": "{cluster_id}",
     "type": "CLUSTER"
 }'
 ~~~
@@ -86,7 +86,7 @@ curl --request POST \
 --url 'https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores' \
 --header "Authorization: Bearer {secret_key}" \
 --json '{
-    "source_cluster_id": "{cluster_id}"
+    "source_cluster_id": "{cluster_id}",
     "type": "DATABASE",
     "objects": [
         {
@@ -107,7 +107,7 @@ curl --request POST \
 --url 'https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores' \
 --header "Authorization: Bearer {secret_key}" \
 --json '{
-    "source_cluster_id": "{cluster_id}"
+    "source_cluster_id": "{cluster_id}",
     "type": "DATABASE",
     "objects": [
         {
@@ -181,7 +181,7 @@ curl --request POST \
 --url 'https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores' \
 --header "Authorization: Bearer {secret_key}" \
 --json '{
-    "source_cluster_id": "{cluster_id}"
+    "source_cluster_id": "{cluster_id}",
     "type": "TABLE",
     "objects": [
         {
@@ -206,7 +206,7 @@ curl --request POST \
 --url 'https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores' \
 --header "Authorization: Bearer {secret_key}" \
 --json '{
-    "source_cluster_id": "{cluster_id}"
+    "source_cluster_id": "{cluster_id}",
     "type": "TABLE",
     "objects": [
         {
@@ -294,7 +294,7 @@ To view the status of a restore job using the cloud API, send a `GET` request to
 ~~~ shell
 curl --request GET \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores/{restore_id} \
---header 'Authorization: Bearer {secret_key}' \
+--header 'Authorization: Bearer {secret_key}'
 ~~~
 
 If the request is successful, the client recieves a response containing JSON describing the status of the specified request operation: