Ref Guide: make sure some URLs aren't hyperlinked; rename "Appendix" section of AWS docs because it looks weird in the middle of the PDF

solr/solr-ref-guide/src/aws-solrcloud-tutorial.adoc

@@ -52,7 +52,7 @@ To use this guide, you must have the following:
  .. You can select one of the existing https://aws.amazon.com/vpc[VPCs] or create a new one.
  .. We need two ports open for our cloud here:
  ... Solr port. In this example we will use Solr's default port 8983.
- ... ZooKeeper Port: We'll use Solr's embedded ZooKeeper, so we'll use the default port 9983 (see the <<appendix,Appendix>> to configure external ZooKeeper).
+ ... ZooKeeper Port: We'll use Solr's embedded ZooKeeper, so we'll use the default port 9983 (see the <<Deploying with External ZooKeeper>> to configure external ZooKeeper).
 .. Click btn:[Inbound] to set inbound network rules, then select btn:[Add Rule]. Select "Custom TCP" as the type. Enter 8983 for the "Port Range" and choose "My IP for the Source, then enter your public IP. Create a second rule with the same type and source, but enter 9983 for the port.
 +
 This will limit access to your current machine. If you want wider access to the instance in order to collaborate with others, you can specify that, but make sure you only allow as much access as needed. A Solr instance should not be exposed to general Internet traffic.
@@ -140,7 +140,7 @@ $ sudo vim /etc/hosts
 +
 In this case, one of the machines will host ZooKeeper embedded along with Solr node, say, `ec2-101-1-2-3.us-east-2.compute.amazonaws.com` (aka, `solr-node-1`)
 +
-See <<appendix,Appendix>> for configure external ZooKeeper.
+See <<Deploying with External ZooKeeper>> for configure external ZooKeeper.
 +
 Inside the `ec2-101-1-2-3.us-east-2.compute.amazonaws.com` (`solr-node-1`)
 +
@@ -174,8 +174,7 @@ You should able to see Solr UI dashboard for both nodes.
 
 You can refer <<solr-tutorial.adoc#exercise-1,Solr Tutorial>> for an extensive walkthrough on creating collections with multiple shards and  replicas, indexing data via different methods and querying documents accordingly.
 
-[[appendix]]
+== Deploying with External ZooKeeper
-== Appendix: Deploy with External ZooKeeper
 
 If you want to configure an external ZooKeeper ensemble to avoid using the embedded single-instance ZooKeeper that runs in the same JVM as the Solr node, you need to make few tweaks in the above listed steps as follows.
 

solr/solr-ref-guide/src/requesthandlers-and-searchcomponents-in-solrconfig.adoc

@@ -26,7 +26,7 @@ These are often referred to as "requestHandler" and "searchComponent", which is
 
 == Request Handlers
 
-Every request handler is defined with a name and a class. The name of the request handler is referenced with the request to Solr, typically as a path. For example, if Solr is installed at ` http://localhost:8983/solr/ `and you have a collection named "```gettingstarted```", you can make a request using URLs like this:
+Every request handler is defined with a name and a class. The name of the request handler is referenced with the request to Solr, typically as a path. For example, if Solr is installed at `\http://localhost:8983/solr/` and you have a collection named "gettingstarted", you can make a request that looks like this:
 
 [source,text]
 ----

solr/solr-ref-guide/src/result-clustering.adoc

@@ -312,9 +312,15 @@ An example XML file changing the default language of documents to Polish is show
 
 The clustering component and Carrot2 clustering algorithms can accept query-time attribute overrides. Note that certain things (for example lexical resources) can only be initialized once (at startup, via the XML configuration files).
 
-An example query that changes the `LingoClusteringAlgorithm.desiredClusterCountBase` parameter for the Lingo algorithm: http://localhost:8983/solr/techproducts/clustering?q=*:*&rows=100&LingoClusteringAlgorithm.desiredClusterCountBase=20.
+An example query that changes the `LingoClusteringAlgorithm.desiredClusterCountBase` parameter for the Lingo algorithm:
 
-The clustering engine (the algorithm declared in `solrconfig.xml`) can also be changed at runtime by passing `clustering.engine=name` request attribute: http://localhost:8983/solr/techproducts/clustering?q=*:*&rows=100&clustering.engine=kmeans
+[source,text]
+http://localhost:8983/solr/techproducts/clustering?q=*:*&rows=100&LingoClusteringAlgorithm.desiredClusterCountBase=20
+
+The clustering engine (the algorithm declared in `solrconfig.xml`) can also be changed at runtime by passing `clustering.engine=name` request attribute:
+
+[source,text]
+http://localhost:8983/solr/techproducts/clustering?q=*:*&rows=100&clustering.engine=kmeans
 
 == Performance Considerations with Dynamic Clustering
 

solr/solr-ref-guide/src/solr-control-script-reference.adoc

@@ -463,7 +463,8 @@ Other collections can share the same configuration by specifying the name of the
 
 The `_default` schema can mutate as data is indexed, since it has schemaless functionality (i.e., data-driven changes to the schema). Consequently, we recommend that you do not share data-driven configurations between collections unless you are certain that all collections should inherit the changes made when indexing data into one of the collections. You can turn off schemaless functionality (i.e., data-driven changes to the schema) for a collection by the following (assuming the collection name is `mycollection`):
 
-`curl http://host:8983/solr/mycollection/config -d '{"set-user-property": {"update.autoCreateFields":"false"}}'`
+[source,text]
+curl http://host:8983/solr/mycollection/config -d '{"set-user-property": {"update.autoCreateFields":"false"}}'
 
 === Delete Core or Collection