Change CTRL + C and CTRL + D to CTRL-C and CTRL-D

Removing spaces ensures that these keyboard shortcuts
won't be split across linebreaks.

Follow-up to cockroachdb#3118

Author: jseldess

CONTRIBUTING.md

@@ -286,7 +286,7 @@ Once you've installed Jekyll and have a local clone of the docs repository, you
 
     - When you make additional changes, Jekyll automatically regenerates the HTML content. No need to stop and re-start Jekyll; just refresh your browser.
 
-    Once you're done viewing your changes, use **CTRL + C** to stop the Jekyll server.
+    Once you're done viewing your changes, use **CTRL-C** to stop the Jekyll server.
 
 3.  Run automated tests against the Jekyll-generate HTML files to check for problems (broken links, missing alt texts for images, etc.):
 

_includes/prod_deployment/secure-test-cluster.md

@@ -23,7 +23,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	> CREATE DATABASE securenodetest;
 	~~~
 
-3. Use `\q` or **CTRL + C** to exit the SQL shell.
+3. Use `\q` or **CTRL-C** to exit the SQL shell.
 
 4. Launch the built-in SQL client against a different node:
 
@@ -52,4 +52,4 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	(5 rows)
 	~~~
 
-6. Use `\q` or **CTRL + C** to exit the SQL shell.
+6. Use `\q` or **CTRL-C** to exit the SQL shell.

v1.0/demo-automatic-cloud-migration.md

@@ -203,9 +203,9 @@ This indicates that all data has been migrated from cloud 1 to cloud 2. In a rea
 
 ## Step 10. Stop the cluster
 
-Once you're done with your cluster, stop YCSB by switching into its terminal and pressing **CTRL + C**. Then do the same for HAProxy and each CockroachDB node.
+Once you're done with your cluster, stop YCSB by switching into its terminal and pressing **CTRL-C**. Then do the same for HAProxy and each CockroachDB node.
 
-{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press <strong>CTRL + C</strong> a second time.{{site.data.alerts.end}}
+{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press <strong>CTRL-C</strong> a second time.{{site.data.alerts.end}}
 
 If you don't plan to restart the cluster, you may want to remove the nodes' data stores and the HAProxy config file:
 

v1.0/demo-automatic-rebalancing.md

@@ -159,9 +159,9 @@ Back in the Admin UI, you'll now see 5 nodes listed. At first, the bytes and rep
 
 ## Step 7.  Stop the cluster
 
-Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL + C**.
+Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL-C**.
 
-{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press <strong>CTRL + C</strong> a second time.{{site.data.alerts.end}}
+{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press <strong>CTRL-C</strong> a second time.{{site.data.alerts.end}}
 
 If you don't plan to restart the cluster, you may want to remove the nodes' data stores:
 

v1.0/demo-data-replication.md

@@ -211,9 +211,9 @@ Back in the Admin UI, you'll see that there are now 5 nodes listed. Again, at fi
 
 ## Step 8.  Stop the cluster
 
-Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL + C**.
+Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL-C**.
 
-{{site.data.alerts.callout_success}}For the last 2 nodes, the shutdown process will take longer (about a minute) and will eventually force kill the nodes. This is because, with only 2 nodes still online, a majority of replicas are no longer available (3 of 5), and so the cluster is not operational. To speed up the process, press <strong>CTRL + C</strong> a second time in the nodes' terminals.{{site.data.alerts.end}}
+{{site.data.alerts.callout_success}}For the last 2 nodes, the shutdown process will take longer (about a minute) and will eventually force kill the nodes. This is because, with only 2 nodes still online, a majority of replicas are no longer available (3 of 5), and so the cluster is not operational. To speed up the process, press <strong>CTRL-C</strong> a second time in the nodes' terminals.{{site.data.alerts.end}}
 
 If you don't plan to restart the cluster, you may want to remove the nodes' data stores:
 

v1.0/demo-fault-tolerance-and-recovery.md

@@ -74,7 +74,7 @@ Exit the SQL shell:
 
 ## Step 3. Remove a node temporarily
 
-In the terminal running node 2, press **CTRL + C** to stop the node.
+In the terminal running node 2, press **CTRL-C** to stop the node.
 
 Alternatively, you can open a new terminal and run the [`cockroach quit`](stop-a-node.html) command against port `26258`:
 
@@ -302,7 +302,7 @@ nodeID:     4
 
 ## Step 9. Remove a node permanently
 
-Again, switch to the terminal running node 2 and press **CTRL + C** to stop it.
+Again, switch to the terminal running node 2 and press **CTRL-C** to stop it.
 
 Alternatively, you can open a new terminal and run the [`cockroach quit`](stop-a-node.html) command against port `26258`:
 
@@ -328,9 +328,9 @@ After about 10 minutes, node 2 will move into a **Dead Nodes** section, indicati
 
 ## Step 11.  Stop the cluster
 
-Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL + C**.
+Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL-C**.
 
-{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press <strong>CTRL + C</strong> a second time.{{site.data.alerts.end}}
+{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press <strong>CTRL-C</strong> a second time.{{site.data.alerts.end}}
 
 If you don't plan to restart the cluster, you may want to remove the nodes' data stores:
 

v1.0/deploy-cockroachdb-on-aws-insecure.md

@@ -210,7 +210,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) as
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 7. Test load balancing
 
@@ -262,7 +262,7 @@ To test this, install CockroachDB locally and use the [built-in SQL client](use-
 	(1 row)
 	~~~
 
-5. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+5. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-aws.md

@@ -332,7 +332,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     > CREATE DATABASE securenodetest;
     ~~~
 
-3. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+3. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 4. Connect the built-in SQL client to node 2, with the `--host` flag set to the external IP address of node 2 and security flags pointing to the CA cert and the client cert and key:
 
@@ -363,7 +363,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     (5 rows)
     ~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Test load balancing
 
@@ -418,7 +418,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     (1 row)
     ~~~
 
-4. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 9. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-digital-ocean-insecure.md

@@ -192,7 +192,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) as
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 7. Test load balancing
 
@@ -244,7 +244,7 @@ To test this, install CockroachDB locally and use the [built-in SQL client](use-
 	(1 row)
 	~~~
 
-5. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+5. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-digital-ocean.md

@@ -309,7 +309,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     > CREATE DATABASE securenodetest;
     ~~~
 
-3. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+3. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 4. Connect the built-in SQL client to node 2, with the `--host` flag set to the address of node 2 and security flags pointing to the CA cert and the client cert and key:
 
@@ -340,7 +340,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     (5 rows)
     ~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Test load balancing
 
@@ -395,7 +395,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     (1 row)
     ~~~
 
-4. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 9. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-google-cloud-platform-insecure.md

@@ -209,7 +209,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) as
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 7. Test load balancing
 
@@ -261,7 +261,7 @@ To test this, install CockroachDB locally and use the [built-in SQL client](use-
 	(1 row)
 	~~~
 
-5. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+5. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-google-cloud-platform.md

@@ -327,7 +327,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	> CREATE DATABASE securenodetest;
 	~~~
 
-3. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+3. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 4. Connect the built-in SQL client to node 2, with the `--host` flag set to the external address of node 2 and security flags pointing to the CA cert and the client cert and key:
 
@@ -358,7 +358,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Test load balancing
 
@@ -414,7 +414,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	(1 row)
 	~~~
 
-4. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 9. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-microsoft-azure-insecure.md

@@ -223,7 +223,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) as
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 7. Test load balancing
 
@@ -275,7 +275,7 @@ To test this, install CockroachDB locally and use the [built-in SQL client](use-
 	(1 row)
 	~~~
 
-5. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+5. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Monitor the cluster
 

v1.0/deploy-cockroachdb-on-microsoft-azure.md

@@ -334,7 +334,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     > CREATE DATABASE securenodetest;
     ~~~
 
-3. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+3. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 4. Launch built-in SQL client with the `--host` flag set to the external address of node 2 and security flags pointing to the CA cert and the client cert and key:
 
@@ -365,7 +365,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     (5 rows)
     ~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Test load balancing
 
@@ -420,7 +420,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
     (1 row)
     ~~~
 
-4.  Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4.  Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 9. Monitor the cluster
 

v1.0/manual-deployment-insecure.md

@@ -135,7 +135,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) as
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 4. Set up HAProxy load balancers
 
@@ -268,7 +268,7 @@ To test this, install CockroachDB locally and use the [built-in SQL client](use-
 	(1 row)
 	~~~
 
-5. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+5. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 6. Configure replication
 

v1.0/manual-deployment.md

@@ -256,7 +256,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	> CREATE DATABASE securenodetest;
 	~~~
 
-3. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+3. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 4. Launch the built-in SQL client with the `--host` flag set to the address of node 2 and security flags pointing to the CA cert and the client cert and key:
 
@@ -287,7 +287,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	(5 rows)
 	~~~
 
-6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+6. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 5. Set up HAProxy load balancers
 
@@ -420,7 +420,7 @@ To test this, use the [built-in SQL client](use-the-built-in-sql-client.html) lo
 	(1 row)
 	~~~
 
-4. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 7. Configure replication
 

v1.0/orchestrate-cockroachdb-with-docker-swarm-insecure.md

@@ -247,7 +247,7 @@ $ sudo docker network create --driver overlay cockroachdb
     > CREATE DATABASE insecurenodetest;
     ~~~
 
-4. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 7. Monitor the cluster
 

v1.0/orchestrate-cockroachdb-with-docker-swarm.md

@@ -467,7 +467,7 @@ A secure CockroachDB cluster uses TLS certificates for encrypted inter-node and
     > CREATE DATABASE securenodetest;
     ~~~
 
-4. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.
+4. Use **CTRL-D**, **CTRL-C**, or `\q` to exit the SQL shell.
 
 ## Step 8. Monitor the cluster
 

v1.0/orchestrate-cockroachdb-with-kubernetes.md

@@ -196,7 +196,7 @@ Kubectl is now configured to use the cluster.
     (1 row)
     ~~~
 
-4. When you're done with the SQL shell, use **CTRL + D**, **CTRL + C**, or `\q` to exit and delete the temporary pod.
+4. When you're done with the SQL shell, use **CTRL-D**, **CTRL-C**, or `\q` to exit and delete the temporary pod.
 
 ## Step 5. Simulate node failure
 

v1.0/secure-a-cluster.md

@@ -216,7 +216,7 @@ The replica count on each node is identical, indicating that all data in the clu
 
 ## Step 6.  Stop the cluster
 
-Once you're done with your test cluster, switch to the terminal running the first node and press **CTRL + C** to stop the node.
+Once you're done with your test cluster, switch to the terminal running the first node and press **CTRL-C** to stop the node.
 
 At this point, with 2 nodes still online, the cluster remains operational because a majority of replicas are available. To verify that the cluster has tolerated this "failure", connect the built-in SQL shell to nodes 2 or 3. You can do this in the same terminal or in a new terminal.
 
@@ -248,9 +248,9 @@ Exit the SQL shell:
 > \q
 ~~~
 
-Now stop nodes 2 and 3 by switching to their terminals and pressing **CTRL + C**.
+Now stop nodes 2 and 3 by switching to their terminals and pressing **CTRL-C**.
 
-{{site.data.alerts.callout_success}}For node 3, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 of 3 nodes left, a majority of replicas are not available, and so the cluster is no longer operational. To speed up the process, press <strong>CTRL + C</strong> a second time.{{site.data.alerts.end}}
+{{site.data.alerts.callout_success}}For node 3, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 of 3 nodes left, a majority of replicas are not available, and so the cluster is no longer operational. To speed up the process, press <strong>CTRL-C</strong> a second time.{{site.data.alerts.end}}
 
 If you don't plan to restart the cluster, you may want to remove the nodes' data stores:
 

v1.0/start-a-local-cluster.md

@@ -185,7 +185,7 @@ The replica count on each node is identical, indicating that all data in the clu
 
 ## Step 5.  Stop the cluster
 
-Once you're done with your test cluster, switch to the terminal running the first node and press **CTRL + C** to stop the node.
+Once you're done with your test cluster, switch to the terminal running the first node and press **CTRL-C** to stop the node.
 
 At this point, with 2 nodes still online, the cluster remains operational because a majority of replicas are available. To verify that the cluster has tolerated this "failure", connect the built-in SQL shell to nodes 2 or 3. You can do this in the same terminal or in a new terminal.
 
@@ -215,9 +215,9 @@ Exit the SQL shell:
 > \q
 ~~~
 
-Now stop nodes 2 and 3 by switching to their terminals and pressing **CTRL + C**.
+Now stop nodes 2 and 3 by switching to their terminals and pressing **CTRL-C**.
 
-{{site.data.alerts.callout_success}}For node 3, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 of 3 nodes left, a majority of replicas are not available, and so the cluster is no longer operational. To speed up the process, press <strong>CTRL + C</strong> a second time.{{site.data.alerts.end}}
+{{site.data.alerts.callout_success}}For node 3, the shutdown process will take longer (about a minute) and will eventually force kill the node. This is because, with only 1 of 3 nodes left, a majority of replicas are not available, and so the cluster is no longer operational. To speed up the process, press <strong>CTRL-C</strong> a second time.{{site.data.alerts.end}}
 
 If you don't plan to restart the cluster, you may want to remove the nodes' data stores:
 

v1.0/stop-a-node.md

@@ -73,7 +73,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
     $ pkill cockroach
     ~~~
 
-    If the node is running in the foreground, press `CTRL + c`.
+    If the node is running in the foreground, press `CTRL-C`.
 
 3. Verify that the `cockroach` process has stopped: