[solr] branch main updated: Fix Zookeeper docs URL link so that it will not get shown (#1136)

[no...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

noble pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new e47f7f0091d Fix Zookeeper docs URL link so that it will not get shown (#1136)
e47f7f0091d is described below

commit e47f7f0091d043d33a9935ac4233119fd83bf9d1
Author: Jeb Nix <11...@users.noreply.github.com>
AuthorDate: Fri Oct 28 06:58:32 2022 +0300

    Fix Zookeeper docs URL link so that it will not get shown (#1136)
---
 .../modules/deployment-guide/pages/solrcloud-shards-indexing.adoc       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc
index cbc20ca9aa2..c9348fdde43 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc
@@ -40,7 +40,7 @@ Additionally, every shard can  have multiple replicas for additional robustness.
 
 In SolrCloud there are no leaders or followers.
 Instead, every shard consists of at least one physical *replica*, exactly one of which is a *leader*.
-Leaders are automatically elected, initially on a first-come-first-served basis, and then based on the ZooKeeper process described at http://zookeeper.apache.org/doc/r{dep-version-zookeeper}/recipes.html#sc_leaderElection.
+Leaders are automatically elected, initially on a first-come-first-served basis, and then based on the ZooKeeper process described at the  http://zookeeper.apache.org/doc/r{dep-version-zookeeper}/recipes.html#sc_leaderElection[Zookeeper docs].
 
 If a leader goes down, one of the other replicas is automatically elected as the new leader.