Updating links in .md files after removing Documentation.

Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
girigupt · Feb 25, 2021 · d41e188 · d41e188
1 parent fa82d11
commit d41e188
Show file tree

Hide file tree

Showing 12 changed files with 229 additions and 229 deletions.
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,2 +1,2 @@
 
-Please read https://etcd.io/docs/current/reporting_bugs/
+Please read https://etcd.io/docs/latest/reporting_bugs/
diff --git a/CHANGELOG-3.0.md b/CHANGELOG-3.0.md
diff --git a/CHANGELOG-3.1.md b/CHANGELOG-3.1.md
diff --git a/CHANGELOG-3.2.md b/CHANGELOG-3.2.md
diff --git a/CHANGELOG-3.3.md b/CHANGELOG-3.3.md
diff --git a/CHANGELOG-3.4.md b/CHANGELOG-3.4.md
diff --git a/CHANGELOG-3.5.md b/CHANGELOG-3.5.md
@@ -11,13 +11,13 @@ The minimum recommended etcd versions to run in **production** are 3.2.28+, 3.3.
 
 ## v3.5.0 (2021 TBD)
 
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.4.0...v3.5.0) and [v3.5 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_5.md) for any breaking changes.
+See [code changes](https://github.com/etcd-io/etcd/compare/v3.4.0...v3.5.0) and [v3.5 upgrade guide](https://etcd.io/docs/latest/upgrades/upgrade_3_5/) for any breaking changes.
 
 - [v3.5.0](https://github.com/etcd-io/etcd/releases/tag/v3.5.0) (2020 TBD), see [code changes](https://github.com/etcd-io/etcd/compare/v3.5.0-rc.1...v3.5.0).
 - [v3.5.0-rc.1](https://github.com/etcd-io/etcd/releases/tag/v3.5.0-rc.1) (2020 TBD), see [code changes](https://github.com/etcd-io/etcd/compare/v3.5.0-rc.0...v3.5.0-rc.1).
 - [v3.5.0-rc.0](https://github.com/etcd-io/etcd/releases/tag/v3.5.0-rc.0) (2020 TBD), see [code changes](https://github.com/etcd-io/etcd/compare/v3.4.0...v3.5.0-rc.0).
 
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.5 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_5.md).**
+**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.5 upgrade guide](https://etcd.io/docs/latest/upgrades/upgrade_3_5/).**
 
 ### Breaking Changes
 
@@ -81,7 +81,7 @@ See [code changes](https://github.com/etcd-io/etcd/compare/v3.4.0...v3.5.0) and
 
 ### Metrics, Monitoring
 
-See [List of metrics](https://github.com/etcd-io/etcd/tree/master/Documentation/metrics) for all metrics per release.
+See [List of metrics](https://etcd.io/docs/latest/metrics/) for all metrics per release.
 
 Note that any `etcd_debugging_*` metrics are experimental and subject to change.
 

diff --git a/CHANGELOG-4.0.md b/CHANGELOG-4.0.md
@@ -11,9 +11,9 @@ The minimum recommended etcd versions to run in **production** are 3.2.28+, 3.3.
 
 ## v4.0.0 (TBD)
 
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.5.0...v4.0.0) and [v4.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_4_0.md) for any breaking changes.
+See [code changes](https://github.com/etcd-io/etcd/compare/v3.5.0...v4.0.0) and [v4.0 upgrade guide](https://etcd.io/docs/latest/upgrades/upgrade_4_0/) for any breaking changes.
 
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v4.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_4_0.md).**
+**Again, before running upgrades from any previous release, please make sure to read change logs below and [v4.0 upgrade guide](https://etcd.io/docs/latest/upgrades/upgrade_4_0/).**
 
 ### Breaking Changes
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -15,7 +15,7 @@ etcd is Apache 2.0 licensed and accepts contributions via GitHub pull requests.
 
 ## Reporting bugs and creating issues
 
-Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](https://github.com/etcd-io/etcd/blob/master/Documentation/reporting-bugs.md) before submitting a bug report. This document might contain links to known issues, another good reason to take a look there before reporting a bug.
+Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](https://etcd.io/docs/latest/reporting-bugs) before submitting a bug report. This document might contain links to known issues, another good reason to take a look there before reporting a bug.
 
 ## Contribution flow
 

diff --git a/Documentation/README.md b/Documentation/README.md
@@ -2,5 +2,5 @@
 
 etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.
 
-These documents have moved to the [etcd-io/website repo](https://github.com/etcd-io/website/), and can be viewed live at [https://etcd.io/docs/current/](https://etcd.io/docs/current/).
+These documents have moved to the [etcd-io/website repo](https://github.com/etcd-io/website/), and can be viewed live at [https://etcd.io/docs/latest/](https://etcd.io/docs/latest/).
 
diff --git a/README.md b/README.md
@@ -192,9 +192,9 @@ See [security disclosure and release process](security/README.md) for details on
 
 ## Issue and PR management
 
-See [issue triage guidelines](Documentation/triage/issues.md) for details on how issues are managed.
+See [issue triage guidelines](https://etcd.io/docs/current/triage/issues/) for details on how issues are managed.
 
-See [PR management](Documentation/triage/PRs.md) for guidelines on how pull requests are managed.
+See [PR management](https://etcd.io/docs/current/triage/prs/) for guidelines on how pull requests are managed.
 
 ## etcd Emeritus Maintainers
 

diff --git a/security/README.md b/security/README.md
@@ -6,7 +6,7 @@ Join the [etcd-dev](https://groups.google.com/forum/?hl=en#!forum/etcd-dev) grou
 
 We’re extremely grateful for security researchers and users that report vulnerabilities to the etcd Open Source Community. All reports are thoroughly investigated by a dedicated committee of community volunteers called [Product Security Committee](security-release-process.md#product-security-committee).
 
-To make a report, please email the private [security@etcd.io](mailto:security@etcd.io) list with the security details and the details expected for [all etcd bug reports](https://github.com/etcd-io/etcd/blob/master/Documentation/reporting_bugs.md).
+To make a report, please email the private [security@etcd.io](mailto:security@etcd.io) list with the security details and the details expected for [all etcd bug reports](https://etcd.io/docs/latest/reporting_bugs/).
 
 ### When Should I Report a Vulnerability?
Original file line number	Diff line number	Diff line change
		@@ -1,2 +1,2 @@

		Please read https://etcd.io/docs/current/reporting_bugs/
		Please read https://etcd.io/docs/latest/reporting_bugs/
Original file line number	Diff line number	Diff line change
Expand Up		@@ -2,5 +2,5 @@

		etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.

		These documents have moved to the [etcd-io/website repo](https://github.com/etcd-io/website/), and can be viewed live at [https://etcd.io/docs/current/](https://etcd.io/docs/current/).
		These documents have moved to the [etcd-io/website repo](https://github.com/etcd-io/website/), and can be viewed live at [https://etcd.io/docs/latest/](https://etcd.io/docs/latest/).