fix v2.3 links

content/en/docs/v2.3/backward_compatibility.md

@@ -19,7 +19,7 @@ The major flag changes are to mostly related to bootstrapping. The `initial-*` f
  - `-peer-heartbeat-interval` is replaced by `-heartbeat-interval`.
  - `-peer-election-timeout` is replaced by `-election-timeout`.
 
-The documentation of new command line flags can be found at [configuration](configuration).
+The documentation of new command line flags can be found at [configuration](../configuration/).
 
 ## Data Directory Naming
 

content/en/docs/v2.3/benchmarks/etcd-2-2-0-rc-benchmarks.md

@@ -72,5 +72,5 @@ Bootstrap another machine and use the [boom HTTP benchmark tool][boom] to send r
 
 [boom]: https://github.com/rakyll/boom
 [c7146bd5]: https://github.com/etcd-io/etcd/commits/c7146bd5f2c73716091262edc638401bb8229144
-[etcd-2.1-benchmark]: etcd-2-1-0-alpha-benchmarks
+[etcd-2.1-benchmark]: ../etcd-2-1-0-alpha-benchmarks/
 [hack-benchmark]: https://github.com/etcd-io/etcd/tree/{{< param git_version_tag >}}/hack/benchmark

content/en/docs/v2.3/clustering.md

@@ -434,11 +434,11 @@ To make understanding this feature easier, we changed the naming of some flags,
 
 [client]: https://github.com/etcd-io/etcd/tree/master/client/v2
 [client-discoverer]: https://pkg.go.dev/github.com/etcd-io/etcd/client#Discoverer
-[conf-adv-client]: configuration#--advertise-client-urls
-[conf-listen-client]: configuration#--listen-client-urls
-[discovery-proto]: discovery_protocol
-[fall-back]: proxy#fallback-to-proxy-mode-with-discovery-service
-[proxy]: proxy
+[conf-adv-client]: ../configuration/#--advertise-client-urls
+[conf-listen-client]: ../configuration/#--listen-client-urls
+[discovery-proto]: ../discovery_protocol/
+[fall-back]: ../proxy/#fallback-to-proxy-mode-with-discovery-service
+[proxy]: ../proxy/
 [rfc-srv]: http://www.ietf.org/rfc/rfc2052.txt
-[runtime-conf]: runtime-configuration
-[runtime-reconf-design]: runtime-reconf-design
+[runtime-conf]: ../runtime-configuration/
+[runtime-reconf-design]: ../runtime-reconf-design/

content/en/docs/v2.3/faq.md

@@ -83,4 +83,4 @@ the clusters. This is probably not what you want.
 Note: --peers flag is now deprecated and --endpoint should be used instead,
 as it might confuse users to give etcdctl a peerURL.
 
-[runtime-reconf-design]: runtime-reconf-design
+[runtime-reconf-design]: ../runtime-reconf-design/

content/en/docs/v2.3/metrics.md

@@ -139,7 +139,7 @@ The Prometheus client library provides a number of metrics under the `go` and `p
 
 Heavy file descriptor (`process_open_fds`) usage (i.e., near the process's file descriptor limit, `process_max_fds`) indicates a potential file descriptor exhaustion issue. If the file descriptors are exhausted, etcd may panic because it cannot create new WAL files.
 
-[glossary-proposal]: glossary#proposal
+[glossary-proposal]: ../glossary/#proposal
 [prometheus]: http://prometheus.io/
 [prometheus-getting-started]: http://prometheus.io/docs/introduction/getting_started/
 [prometheus-naming]: http://prometheus.io/docs/practices/naming/

content/en/docs/v2.3/proxy.md

@@ -149,7 +149,7 @@ sudo systemd restart etcd
 
 If an error occurs, check the [add member troubleshooting doc][runtime-configuration].
 
-[discovery-service]: clustering#discovery
+[discovery-service]: ../clustering/#discovery
 [goreman]: https://github.com/mattn/goreman
 [procfile]: https://github.com/etcd-io/etcd/blob/master/Procfile.v2
-[runtime-configuration]: runtime-configuration#error-cases-when-adding-members
+[runtime-configuration]: ../runtime-configuration/#error-cases-when-adding-members

content/en/docs/v2.3/upgrade_2_3.md

@@ -20,7 +20,7 @@ Also, to ensure a smooth rolling upgrade, the running cluster must be healthy. Y
 
 Before upgrading etcd, always test the services relying on etcd in a staging environment before deploying the upgrade to the production environment.
 
-Before beginning,  [backup the etcd data directory](admin_guide#backing-up-the-datastore). Should something go wrong with the upgrade, it is possible to use this backup to[downgrade](#downgrade) back to existing etcd version.
+Before beginning,  [backup the etcd data directory](../admin_guide/#backing-up-the-datastore). Should something go wrong with the upgrade, it is possible to use this backup to[downgrade](#downgrade) back to existing etcd version.
 
 #### Mixed Versions
 
@@ -36,7 +36,7 @@ For a much larger total data size, 100MB or more , this one-time process might t
 
 If all members have been upgraded to v2.3, the cluster will be upgraded to v2.3, and downgrade from this completed state is **not possible**. If any single member is still v2.2, however, the cluster and its operations remains “v2.2”, and it is possible from this mixed cluster state to return to using a v2.2 etcd binary on all members.
 
-Please [backup the data directory](admin_guide#backing-up-the-datastore) of all etcd members to make downgrading the cluster possible even after it has been completely upgraded.
+Please [backup the data directory](../admin_guide/#backing-up-the-datastore) of all etcd members to make downgrading the cluster possible even after it has been completely upgraded.
 
 ### Upgrade Procedure