Merge pull request #265 from KxSystems/KXI-37739-2

Fix README

README.md

@@ -115,7 +115,7 @@ This runs a q session using the existing kdb installed as part of the kdb VS Cod
 
 **Step 6**: Click **Create connection** to confirm the _connection creation_
 
-**Step 7**: Right-click the q bundled process listed under _KX:CONNECTIONS_, and click _Start q process_.”
+**Step 7**: Right-click the q bundled process listed under _KX:CONNECTIONS_, and click _Start q process_.
 
 ![setendpoint](https://github.com/KxSystems/kx-vscode/blob/main/img/managedqprocess.jpg?raw=true)
 
@@ -135,7 +135,7 @@ If you close the extension, the connection to the child q process also closes.
 
 ![setendpoint](https://github.com/KxSystems/kx-vscode/blob/main/img/myq.png?raw=true)
 
-**Step 4**: Assign a _server name / alias_. The server name selected **cannot be `local` or `insights`**, as these are reserved for use by [managed q sessions](#bundled-q) and [kdb Insights Enterprise connections](#insights-connection); e.g. _dev_
+**Step 4**: Assign a _server name / alias_. The server name selected **cannot be `local` or `insights`**, as these are reserved for use by [Bundled q connections](#bundled-q) and [Insights connections](#insights-connection), respectively; e.g. dev
 
 **Step 5**: Set the _connection address_ or ip address of the kdb server; e.g. _localhost_.
 
@@ -165,7 +165,7 @@ For kdb Insights Enterprise, the kdb VS Code extension is using a shared kdb pro
 
 ![connecttoinsights](https://github.com/KxSystems/kx-vscode/blob/main/img/insightsconnection.png?raw=true)
 
-**Step 3**: Create a _server name / alias_; this can be any name, aside from local`, which is used by q [bundled connection](#bundled-q).
+**Step 3**: Create a _server name / alias_; this can be any name, aside from `local`, which is used by [Bundled q connection](#bundled-q).
 
 **Step 4**: Set the _hostname_. This is the remote address of your kdb Insights Enterprise deployment: e.g `https://mykdbinsights.cloudapp.azure.com`