Improvements to Getting Started docs

[Amruta-Ranade]

1. Install CockroachDB
2. Try out any or all of the following tutorials:
   • Data replication
   • Fault Tolerance and Recovery
   • Automatic Rebalancing
   • Follow the workload
3. Comment on this issue with your feedback about the clarity, correctness, and ease-of-use of the docs.

[kbatuigas]

From Install CockroachDB for Windows:

• Step 2 under "Download the Binary" - copying to clipboard copies directory path, but only .\cockroach.exe version is necessary after having navigated to directory

[kbatuigas]

From Start a Local Cluster (Insecure):

• Code snippet under Step 1. Start the first node copies as cockroach start --insecure --host=localhost into Windows Powershell, resulting in an error "The term 'cockroach' is not registered as the name...". Adding ./ (i.e. ./cockroach start --insecure --host=localhost ) allows the command to run successfully

[dianaprince]

On step 3, when testing the cluster, I closed the terminal for Node 1 which resulted in "files still in use" errors when attempting to stop the cluster on step 5.

[dianaprince]

Minor grammatical notes: write out the number when the number is less than ten. For example, "3 or more nodes" should be "three or more nodes."

Also, punctuation goes inside quotation marks, so on step 5 "failure", should be "failure,"

[kbatuigas]

From Start a Local Cluster (Insecure):

• Under Step 3. Test the Cluster: running ./cockroach sql --insecure in Windows Powershell ISE (x86) appears to connect to the SQL shell, but the terminal isn't "responsive" (i.e. the cursor doesn't appear, and nothing happens when you try to type anything). However, it runs and connects fine in Windows Powershell, and I am able to type and run SQL statements.

[jseldess]

From @lleonard-msft:

In Step 3 of Start a Local Cluster, the use of ports for the SQL client is a bit confusing to a newbie. Perhaps a simple sentence mentioning the default port after starting the session would help.

[jseldess]

Thank you for this feedback, @dianaprince, @kbatuigas, and @lleonard-msft!