Master -> Main on CL links (hashicorp#12286)

jartek · Sep 11, 2021 · fc79c86 · fc79c86
1 parent ef859a6
commit fc79c86
Show file tree

Hide file tree

Showing 7 changed files with 7 additions and 7 deletions.
diff --git a/website/content/docs/release-notes/1.5.0.mdx b/website/content/docs/release-notes/1.5.0.mdx
@@ -60,4 +60,4 @@ description: |-
 
 `audit:` Added `mount_type` field to requests and responses
 
-**For more detailed information, please refer to the [Changelog](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md)**
+**For more detailed information, please refer to the [Changelog](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md)**
diff --git a/website/content/docs/release-notes/1.6.0.mdx b/website/content/docs/release-notes/1.6.0.mdx
@@ -49,4 +49,4 @@ to be used in conjunction with Microsoft’s Azure Key Vault.
 - Vault 1.6 will use Go 1.15, which has dropped support for 32-bit binaries for [Darwin](https://golang.org/doc/go1.15#darwin),
   so we will no longer be issuing `darwin_386` builds of Vault.
 
-For more detailed information, please refer to the [Changelog](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#160).
+For more detailed information, please refer to the [Changelog](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#160).
diff --git a/website/content/docs/release-notes/1.7.0.mdx b/website/content/docs/release-notes/1.7.0.mdx
@@ -61,4 +61,4 @@ description: |-
 - There is a known issue that may cause Autopilot to be unable to determine the leader node. This occurs if the IP in the raft peer list is different from the configured cluster address. If affected you should disable Autopilot by setting the VAULT_RAFT_AUTOPILOT_DISABLE environment variable to 1.
 - Autopilot is not currently supported with Integrated Storage's HA-only mode or with DR secondary clusters.
 
-For more detailed information, please refer to the [Changelog](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#170).
+For more detailed information, please refer to the [Changelog](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#170).
diff --git a/website/content/docs/upgrading/upgrade-to-1.1.0.mdx b/website/content/docs/upgrading/upgrade-to-1.1.0.mdx
@@ -40,7 +40,7 @@ past. In these reindex scenarios, the secondary cluster will perform a complete
 WAL replay, which can take a long time and is a partially blocking operation.
 
 This is fixed in [Vault
-1.1.3](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#113-june-5th-2019),
+1.1.3](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#113-june-5th-2019),
 and we recommend upgrading to Vault 1.1.3+ rather than any prior 1.1.x version.
 We also strongly recommend upgrading your Vault cluster to 1.1.3 if you are
 running Vault Enterprise 1.1.0, 1.1.1 or 1.1.2.
diff --git a/website/content/docs/upgrading/upgrade-to-1.1.1.mdx b/website/content/docs/upgrading/upgrade-to-1.1.1.mdx
@@ -45,7 +45,7 @@ past. In these reindex scenarios, the secondary cluster will perform a complete
 WAL replay, which can take a long time and is a partially blocking operation.
 
 This is fixed in [Vault
-1.1.3](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#113-june-5th-2019),
+1.1.3](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#113-june-5th-2019),
 and we recommend upgrading to Vault 1.1.3+ rather than any prior 1.1.x version.
 We also strongly recommend upgrading your Vault cluster to 1.1.3 if you are
 running Vault Enterprise 1.1.0, 1.1.1 or 1.1.2.

diff --git a/website/content/docs/upgrading/upgrade-to-1.1.2.mdx b/website/content/docs/upgrading/upgrade-to-1.1.2.mdx
@@ -22,7 +22,7 @@ past. In these reindex scenarios, the secondary cluster will perform a complete
 WAL replay, which can take a long time and is a partially blocking operation.
 
 This is fixed in [Vault
-1.1.3](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#113-june-5th-2019),
+1.1.3](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#113-june-5th-2019),
 and we recommend upgrading to Vault 1.1.3+ rather than any prior 1.1.x version.
 We also strongly recommend upgrading your Vault cluster to 1.1.3 if you are
 running Vault Enterprise 1.1.0, 1.1.1 or 1.1.2.
diff --git a/website/content/guides/operations/production.mdx b/website/content/guides/operations/production.mdx
@@ -94,7 +94,7 @@ and practical.
   is important to incorporate security fixes and any changes in default
   settings such as key lengths or cipher suites. Subscribe to the [Vault
   mailing list](https://groups.google.com/forum/#!forum/vault-tool) and [GitHub
-  CHANGELOG](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md) for
+  CHANGELOG](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md) for
   updates.
 
 - **Configure SELinux / AppArmor**. Using additional mechanisms like SELinux