Fix outdated docs links

specification/resources/databases/databases_add_connectionPool.yml

@@ -5,7 +5,7 @@ summary: Add a New Connection Pool (PostgreSQL)
 description: |
   For PostgreSQL database clusters, connection pools can be used to allow a
   database to share its idle connections. The popular PostgreSQL connection
-  pooling utility PgBouncer is used to provide this service. [See here for more information](https://www.digitalocean.com/docs/databases/postgresql/how-to/manage-connection-pools/)
+  pooling utility PgBouncer is used to provide this service. [See here for more information](https://docs.digitalocean.com/products/databases/postgresql/how-to/manage-connection-pools/)
   about how and why to use PgBouncer connection pooling including
   details about the available transaction modes.
 

specification/resources/databases/databases_update_firewall_rules.yml

@@ -11,7 +11,7 @@ description: >-
   provided, any Droplet or Kubernetes node with that tag applied to it will
   have access. The firewall is limited to 100 rules (or trusted sources). When
   possible, we recommend
-  [placing your databases into a VPC network](https://www.digitalocean.com/docs/networking/vpc/)
+  [placing your databases into a VPC network](https://docs.digitalocean.com/products/networking/vpc/)
   to limit access to them instead of using a firewall.
 
   A successful

specification/resources/kubernetes/kubernetes_create_cluster.yml

@@ -10,7 +10,7 @@ description: |
   The request may contain a maintenance window policy describing a time period
   when disruptive maintenance tasks may be carried out. Omitting the policy
   implies that a window will be chosen automatically. See
-  [here](https://www.digitalocean.com/docs/kubernetes/how-to/upgrade-cluster/)
+  [here](https://docs.digitalocean.com/products/kubernetes/how-to/upgrade-cluster/)
   for details.
 
 tags:

specification/resources/kubernetes/kubernetes_get_credentials.yml

@@ -9,7 +9,7 @@ description: |
   The resulting JSON object contains token-based authentication for clusters
   supporting it, and certificate-based authentication otherwise. For a list of
   supported versions and more information, see "[How to Connect to a DigitalOcean
-  Kubernetes Cluster with kubectl](https://www.digitalocean.com/docs/kubernetes/how-to/connect-with-kubectl/)".
+  Kubernetes Cluster](https://docs.digitalocean.com/products/kubernetes/how-to/connect-to-cluster/)".
 
   To retrieve credentials for accessing a Kubernetes cluster, send a GET
   request to `/v2/kubernetes/clusters/$K8S_CLUSTER_ID/credentials`.

specification/resources/kubernetes/kubernetes_get_kubeconfig.yml

@@ -10,7 +10,7 @@ description: |
   The resulting kubeconfig file uses token-based authentication for clusters
   supporting it, and certificate-based authentication otherwise. For a list of
   supported versions and more information, see "[How to Connect to a DigitalOcean
-  Kubernetes Cluster with kubectl](https://www.digitalocean.com/docs/kubernetes/how-to/connect-with-kubectl/)".
+  Kubernetes Cluster](https://docs.digitalocean.com/products/kubernetes/how-to/connect-to-cluster/)".
 
   To retrieve a kubeconfig file for use with a Kubernetes cluster, send a GET
   request to `/v2/kubernetes/clusters/$K8S_CLUSTER_ID/kubeconfig`.

specification/resources/registry/registry_run_garbageCollection.yml

@@ -7,7 +7,7 @@ description: |
   manifest data) after deleting one or more manifests from a repository. If
   there are no unreferenced blobs resulting from the deletion of one or more
   manifests, garbage collection is effectively a noop.
-  [See here for more information](https://www.digitalocean.com/docs/container-registry/how-to/clean-up-container-registry/)
+  [See here for more information](https://docs.digitalocean.com/products/container-registry/how-to/clean-up-container-registry/)
   about how and why you should clean up your container registry periodically.
 
   To request a garbage collection run on your registry, send a POST request to

specification/resources/volumes/volumeActions_post.yml

@@ -20,7 +20,7 @@ description: |
   volumes may be attached to a Droplet at a time. Pre-formatted volumes will be
   automatically mounted to Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS
   Droplets created on or after April 26, 2018 when attached. On older Droplets,
-  [additional configuration](https://www.digitalocean.com/community/tutorials/how-to-partition-and-format-digitalocean-block-storage-volumes-in-linux#mounting-the-filesystems)
+  [additional configuration](https://docs.digitalocean.com/products/volumes/how-to/mount/)
   is required.
 
   ## Remove a Block Storage Volume from a Droplet

specification/resources/volumes/volumeActions_post_byId.yml

@@ -19,7 +19,7 @@ description: |
   volumes may be attached to a Droplet at a time. Pre-formatted volumes will be
   automatically mounted to Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS
   Droplets created on or after April 26, 2018 when attached. On older Droplets,
-  [additional configuration](https://www.digitalocean.com/community/tutorials/how-to-partition-and-format-digitalocean-block-storage-volumes-in-linux#mounting-the-filesystems)
+  [additional configuration](https://docs.digitalocean.com/products/volumes/how-to/mount/)
   is required.
 
   ## Remove a Block Storage Volume from a Droplet