From efaa9b7fb14e2d9aa51ee9e13bee12cdc28eb981 Mon Sep 17 00:00:00 2001
From: Philip Carneiro <pcarneiro@kx.com>
Date: Tue, 24 Oct 2023 10:44:07 +0100
Subject: [PATCH 1/3] add documentation

---
 README.md | 174 +++++++++++++++++++++++++-----------------------------
 1 file changed, 80 insertions(+), 94 deletions(-)

diff --git a/README.md b/README.md
index 116ad904..12a12da3 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,8 @@
 # kdb Visual Studio Code extension
 
-This is a companion extension for kdb developers to edit q files, connect to kdb processes, and run queries.  This VS Code extension can be used alongside [kdb Insights Enterprise](https://code.kx.com/insights/enterprise/index.html) when using a shared kdb process. 
+This is a companion extension for kdb developers to edit q files, connect to kdb processes, and run queries. This VS Code extension can be used alongside [kdb Insights Enterprise](https://code.kx.com/insights/enterprise/index.html) when using a shared kdb process.
 
-Please use vscode-questions@kx.com to raise any questions, issues or feedback. 
+Please use vscode-questions@kx.com to raise any questions, issues or feedback.
 
 <!--
 [![KX VS Code CI Testing](https://github.com/KxSystems/kx-vscode/actions/workflows/ci.yml/badge.svg)](https://github.com/KxSystems/kx-vscode/actions/workflows/ci.yml)
@@ -21,34 +21,31 @@ Please use vscode-questions@kx.com to raise any questions, issues or feedback.
 - [Settings](#settings)
 - [Shortcuts](#shortcuts)
 
-
 ## Why q for VS Code?
 
 With the kdb VS Code extension you can:
 
 - Install q.
 - Write q syntax with support for predict and autocomplete.
-- Execute q from a single line of code, code block or q file. 
+- Execute q from a single line of code, code block or q file.
 - Write and execute q code against kdb Insights Enterprise.
 - View results from your queries.
 
-
 ## Get started
 
 If you have an existing q installation, you will see the message `q runtime installed` and can go directly to adding [connections](#connections).
 
 If you are new to q, you can install q with the kdb VS Code extension; see [install q](#install-q).
 
-
 ### Install q
 
-**Step 1**: Download the latest version of kdb+.  Different versions of kdb+ are available, and the version you download will determine the supported features in VS Code:
+**Step 1**: Download the latest version of kdb+. Different versions of kdb+ are available, and the version you download will determine the supported features in VS Code:
 
-item | write q | run q queries | explore results | shared kdb process with kdb Insights
----- | ------- | ------------- | --------------- | ----------------------------------
-[kdb+ Personal Edition](https://kx.com/kdb-personal-edition-download/) | yes | yes | yes | no
-[kdb Insights Personal Edition](https://kx.com/kdb-insights-personal-edition-license-download/)  | yes | yes | yes | no
-kdb Insights Enterprise | yes | yes | yes | yes            
+| item                                                                                            | write q | run q queries | explore results | shared kdb process with kdb Insights |
+| ----------------------------------------------------------------------------------------------- | ------- | ------------- | --------------- | ------------------------------------ |
+| [kdb+ Personal Edition](https://kx.com/kdb-personal-edition-download/)                          | yes     | yes           | yes             | no                                   |
+| [kdb Insights Personal Edition](https://kx.com/kdb-insights-personal-edition-license-download/) | yes     | yes           | yes             | no                                   |
+| kdb Insights Enterprise                                                                         | yes     | yes           | yes             | yes                                  |
 
 Contact licadmin@kx.com for commercial kdb licensing.
 
@@ -56,35 +53,35 @@ Contact licadmin@kx.com for commercial kdb licensing.
 
 Extract the file to a directory; instructions are available for [Linux, macOS and Windows](https://code.kx.com/q/learn/install/#step-2-unzip-your-download).
 
-* I want to learn more about [kdb+ installation](https://code.kx.com/q/learn/install/)
+- I want to learn more about [kdb+ installation](https://code.kx.com/q/learn/install/)
 
-**Step 3**: The welcome email will also have your kdb, `k4.lic` or `kc.lic` license as an attachment.  We recommend you add your kdb license to your q installation directory, or `QHOME`, and define this location in your environment variables.  It is essential you define an environment variable for VS Code to recognize a valid license.   
+**Step 3**: The welcome email will also have your kdb, `k4.lic` or `kc.lic` license as an attachment. We recommend you add your kdb license to your q installation directory, or `QHOME`, and define this location in your environment variables. It is essential you define an environment variable for VS Code to recognize a valid license.
 
-*Note*: If your kdb license is stored outside of your q  (`QHOME`) directory, create a `QLIC` environment variable instead.
+_Note_: If your kdb license is stored outside of your q (`QHOME`) directory, create a `QLIC` environment variable instead.
 
-* I want to learn [how to define a QHOME environment variable](https://code.kx.com/q/learn/install/#step-5-edit-your-profile).
+- I want to learn [how to define a QHOME environment variable](https://code.kx.com/q/learn/install/#step-5-edit-your-profile).
 
 ### Install q with VS Code.
 
 You can install q from the VS Code extension. You still need to register for [kdb Insights Personal Edition](https://kx.com/kdb-insights-personal-edition-license-download/) to obtain a license and VS Code will guide you through steps to install. The license will be incorporated as part of the kdb VS Code extension, although a `QHOME` environment variable is still required if you wish to utilise the q installation outside of VS Code.
 
-**Step 1**: Click `Install new instance` from the prompt if no q installation is flagged. If this prompt is cancelled, then use the aforementioned [install q](#install-q). 
+**Step 1**: Click `Install new instance` from the prompt if no q installation is flagged. If this prompt is cancelled, then use the aforementioned [install q](#install-q).
 
 ![installnewinstance](https://code.kx.com/img/vscode/installnewinstance.jpg)
 
-**Step 2**: If you have already registered for kdb+ or kdb Insights, then choose `Select/Enter a license`.  If you haven't registered, choose `Acquire license`, this will open a dialog with a redirect link to register for [kdb Insights Personal Edition](https://kx.com/kdb-insights-personal-edition-license-download/). 
+**Step 2**: If you have already registered for kdb+ or kdb Insights, then choose `Select/Enter a license`. If you haven't registered, choose `Acquire license`, this will open a dialog with a redirect link to register for [kdb Insights Personal Edition](https://kx.com/kdb-insights-personal-edition-license-download/).
 
 ![findlicense](https://code.kx.com/img/vscode/findlicense.jpg)
 
-**Step 3**: With the license secured, you can then link this to VS Code by either `pasting license string` or `selecting license file` from your PC; the latter method is recommended for new users. 
+**Step 3**: With the license secured, you can then link this to VS Code by either `pasting license string` or `selecting license file` from your PC; the latter method is recommended for new users.
 
 ![findlicense](https://code.kx.com/img/vscode/pastelicense.jpg)
 
-The base64 encoded license string can be found in the welcome email received after registration, under the download link for the license file. 
+The base64 encoded license string can be found in the welcome email received after registration, under the download link for the license file.
 
 ![welcomeemaillicense](https://code.kx.com/img/vscode/weclomeemail.jpg)
 
-The `k4.lic` or `kc.lic` license file can be downloaded to your PC. 
+The `k4.lic` or `kc.lic` license file can be downloaded to your PC.
 
 **Step 4**: Set a [`QHOME` environment variable](https://code.kx.com/q/learn/install/#step-5-edit-your-profile) to the location used by the kdb VS Code install. A notification dialog displays the location of q, as do the extension [settings](#settings). This will allows you to use q outside of VSCode.
 
@@ -92,7 +89,7 @@ The `k4.lic` or `kc.lic` license file can be downloaded to your PC.
 
 If q is installed at `C:\q`, then `QHOME` is `C:\q`.
 
-To finish, a prompt is offered with an opt-in to receive a newsletter.  
+To finish, a prompt is offered with an opt-in to receive a newsletter.
 
 ## Connections
 
@@ -102,7 +99,7 @@ The kdb VS Code extension allows you to connect VS Code to a q process; this can
 
 **Step 1**: Identify the remote location of a running process. The hostname and port will be required along with any authentication information.
 
-**Step 2**: Within the kdb VS Code extension, click *connect to kdb server*, or *Add new connection** from the *CONNECTIONS* context menu.
+**Step 2**: Within the kdb VS Code extension, click _connect to kdb server_, or *Add new connection\*\* from the *CONNECTIONS\* context menu.
 
 ![connecttoakdbserver](https://code.kx.com/img/vscode/connecttoakdbserver.png)
 
@@ -110,34 +107,33 @@ The kdb VS Code extension allows you to connect VS Code to a q process; this can
 
 ![setendpoint](https://code.kx.com/img/vscode/step1connecttoakdbserver.jpg)
 
-**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](#managed-q-session) and [kdb Insights Enterprise connections](#kdb-insights-enterprise); 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 [managed q sessions](#managed-q-session) and [kdb Insights Enterprise connections](#kdb-insights-enterprise); e.g. _dev_
 
-**Step 5**: Set the *hostname* or ip address of the kdb server; e.g. *localhost*.
+**Step 5**: Set the _hostname_ or ip address of the kdb server; e.g. _localhost_.
 
-**Step 6**: Set the *port* used by the kdb server; e.g. *5001*. 
+**Step 6**: Set the _port_ used by the kdb server; e.g. _5001_.
 
-* I want to learn more about [setting a q port](https://code.kx.com/q/basics/ipc/)
+- I want to learn more about [setting a q port](https://code.kx.com/q/basics/ipc/)
 
-**Step 7**: If authentication is required, define the *username*, then the *password*; clicking Enter with these inputs blank skips these steps.
+**Step 7**: If authentication is required, define the _username_, then the _password_; clicking Enter with these inputs blank skips these steps.
 
-**Step 8**: An option to enable TLS encryption is offered; the default is *false*.
+**Step 8**: An option to enable TLS encryption is offered; the default is _false_.
 
-* I want to learn more [about TLS encryption](https://code.kx.com/q/kb/ssl/).
+- I want to learn more [about TLS encryption](https://code.kx.com/q/kb/ssl/).
 
-Upon completion, the localhost connection appears under *KX:CONNECTIONS* in the left hand panel.
+Upon completion, the localhost connection appears under _KX:CONNECTIONS_ in the left hand panel.
 
 ![localkdbconnection](https://code.kx.com/img/vscode/localkdbconnection.jpg)
 
-**Step 9**: Right-click the connection to *connect kdb server*.  Ensure the q process is running.
+**Step 9**: Right-click the connection to _connect kdb server_. Ensure the q process is running.
 
 ![localkdbconnection](https://code.kx.com/img/vscode/connectserver.jpg)
 
-
 ### Managed q session
 
 This runs a q session using the existing kdb installed as part of the kdb VS Code extension.
 
-**Step 1**: Click *connect to kdb server* or *Add new connection* from the *CONNECTIONS* context menu.
+**Step 1**: Click _connect to kdb server_ or _Add new connection_ from the _CONNECTIONS_ context menu.
 
 ![connecttoakdbserver](https://code.kx.com/img/vscode/connecttoakdbserver.png)
 
@@ -145,56 +141,53 @@ This runs a q session using the existing kdb installed as part of the kdb VS Cod
 
 ![setendpoint](https://code.kx.com/img/vscode/step1connecttoakdbserver.jpg)
 
-**Step 3**: Set the *server name / alias* to `local`.
+**Step 3**: Set the _server name / alias_ to `local`.
 
-**Step 4**: Set the *hostname*; e.g. *localhost*
+**Step 4**: Set the _hostname_; e.g. _localhost_
 
-**Step 5**: Set the *port* for the kdb server. Ensure the port used doesn't conflict with any other running q process; e.g. *5002*
+**Step 5**: Set the _port_ for the kdb server. Ensure the port used doesn't conflict with any other running q process; e.g. _5002_
 
-* I want to learn more about [setting a q port](https://code.kx.com/q/basics/ipc/)
+- I want to learn more about [setting a q port](https://code.kx.com/q/basics/ipc/)
 
-**Step 6**: Right-click the managed q process listed under *KX:CONNECTIONS*, and click *Start q process*.
+**Step 6**: Right-click the managed q process listed under _KX:CONNECTIONS_, and click _Start q process_.
 
 ![setendpoint](https://code.kx.com/img/vscode/managedqprocess.jpg)
 
-**Step 7**: From the same right-click menu, click *Connect kdb server*.  This connects to the child q process running inside the kdb VS Code extension. 
-
-If you close the extension, the connection to the child q process also closes. 
+**Step 7**: From the same right-click menu, click _Connect kdb server_. This connects to the child q process running inside the kdb VS Code extension.
 
+If you close the extension, the connection to the child q process also closes.
 
 ### kdb Insights Enterprise
 
-For kdb Insights Enterprise, the kdb VS Code extension is using a shared kdb process.  Unlike for a **managed q session**, you must have [kdb Insights Enterprise Personal Edition](https://trykdb.kx.com/kx/signup) running before using these connections. 
+For kdb Insights Enterprise, the kdb VS Code extension is using a shared kdb process. Unlike for a **managed q session**, you must have [kdb Insights Enterprise Personal Edition](https://trykdb.kx.com/kx/signup) running before using these connections.
 
-**Step 1**: Click *connect to kdb server*.
+**Step 1**: Click _connect to kdb server_.
 
 ![connecttoakdbserver](https://code.kx.com/img/vscode/connecttoakdbserver.png)
 
-**Step 2**: When prompted to select a kdb type, choose *Connect to kdb insights*
+**Step 2**: When prompted to select a kdb type, choose _Connect to kdb insights_
 
 ![connecttoinsights](https://code.kx.com/img/vscode/connecttoinsights.jpg)
 
-**Step 3**: Create a *server name / alias*; this can be any name, aside from `local`, which is used by the [managed q session](#managed-q-session).
+**Step 3**: Create a _server name / alias_; this can be any name, aside from `local`, which is used by the [managed q session](#managed-q-session).
 
-**Step 4**: Set the *hostname*. This is the remote address of your kdb Insights Enterprise deployment: e.g `https://mykdbinsights.cloudapp.azure.com`
+**Step 4**: Set the _hostname_. This is the remote address of your kdb Insights Enterprise deployment: e.g `https://mykdbinsights.cloudapp.azure.com`
 
-**Step 5**: The kdb Insights Enterprise connection is listed under *KX:Connections*, with its own icon.  Right-click the connection and *Connect to Insights*
+**Step 5**: The kdb Insights Enterprise connection is listed under _KX:Connections_, with its own icon. Right-click the connection and _Connect to Insights_
 
 ![connecttoinsights](https://code.kx.com/img/vscode/kdbinsightsconnection.jpg)
 
-**Step 6**: The kdb VS Code extension runs an authentication step with the remote kdb Insights Enterprise process; sign-in to kdb Insights Enterprise. 
+**Step 6**: The kdb VS Code extension runs an authentication step with the remote kdb Insights Enterprise process; sign-in to kdb Insights Enterprise.
 
 ![authenticateinsights](https://code.kx.com/img/vscode/insightsauthenticate.jpg)
 
-After a successful connection to a kdb Insights Enterprise process, a new *DATA SOURCES* panel will become available in the kdb VS Code extension.
+After a successful connection to a kdb Insights Enterprise process, a new _DATA SOURCES_ panel will become available in the kdb VS Code extension.
 
 ![insightsdatasources](https://code.kx.com/img/vscode/datasources.jpg)
 
-
 Once connected to a q process, go to [execute code](#execute-code).
 
-[//]: # (In what context is the reserved alias name `insights` used? - BMA - the context is used on build the connection tree; different icon; different connection process. - DF - Is this connection process currently supported in kdb VS Code extension; if so, do we need to document it here?)
-
+[//]: # "In what context is the reserved alias name `insights` used? - BMA - the context is used on build the connection tree; different icon; different connection process. - DF - Is this connection process currently supported in kdb VS Code extension; if so, do we need to document it here?"
 
 ## kdb language server
 
@@ -204,7 +197,6 @@ A kdb language server is bundled with the kdb VS Code extension. It offers vario
 - [Code navigation](#code-navigation)
 - [Code completion](#code-completion)
 
-
 ### Syntax highlighting
 
 The extension provides keyword syntax highlighting, comments and linting help.
@@ -213,7 +205,6 @@ The extension provides keyword syntax highlighting, comments and linting help.
 
 ![Linting](https://code.kx.com/img/vscode/linting.png)
 
-
 ### Code navigation
 
 While developing q scripts, the kdb VS Code extension supports:
@@ -223,7 +214,7 @@ While developing q scripts, the kdb VS Code extension supports:
   Navigate to the definition of a function
 
 - Find/go to all references
-  
+
   View references of a function both on the side view and inline with the editor
 
   ![Find all references](https://code.kx.com/img/vscode/find-all-references.png)
@@ -232,13 +223,12 @@ While developing q scripts, the kdb VS Code extension supports:
 
 ### Code Completion
 
-- Keyword auto complete for the q language 
+- Keyword auto complete for the q language
 
   ![Autocomplete](https://code.kx.com/img/vscode/autocomplete.png)
 
 - Autocomplete for local and remotely connected q processes
 
-
 ## Execute code
 
 Leaning on VS Code's extensive integrations with SCMs, all code is typically stored and loaded into a VS Code workspace. From there, the kdb VS Code extension allows you execute code against both kdb processes, and kdb Insights Enterprise endpoints.
@@ -249,16 +239,15 @@ There are three options available from the right-click menu for executing code:
 
 - Execute current selection
 
-    Takes the current selection (or current line if nothing is selected) and executes it against the connected q process. Results are displayed in the [output window and/or the kdb results window](#view-results).
+  Takes the current selection (or current line if nothing is selected) and executes it against the connected q process. Results are displayed in the [output window and/or the kdb results window](#view-results).
 
 - Execute entire file
 
-    Takes the current file and executes it against the connected q process. Results are displayed in the [output window](#view-results). Returned data are displayed in the [kdb results window](#view-results).
+  Takes the current file and executes it against the connected q process. Results are displayed in the [output window](#view-results). Returned data are displayed in the [kdb results window](#view-results).
 
 - Run q file in new q instance
 
-    If q is installed and executable from the terminal, you can execute an entire script on a newly launched q instance. Executing a file on a new instance is done in the terminal, and allows interrogation of the active q process from the terminal window.
-
+  If q is installed and executable from the terminal, you can execute an entire script on a newly launched q instance. Executing a file on a new instance is done in the terminal, and allows interrogation of the active q process from the terminal window.
 
 ### Insights query execution
 
@@ -273,9 +262,7 @@ kdb Insights Enterprise supports the use of data sources, where you can build a
 To create a data source:
 
 1. In the Data Sources view, click the Options button and select 'Add Data Source'.
-    
 1. Click on the created data source where the name, API and parameterization can be applied.
-    
 1. Click Save to persist the data source to the VS Code workspace.
 
 ![data Source](https://code.kx.com/img/vscode/data-source.png)
@@ -286,52 +273,53 @@ In addition to API queries, if the query environment is enabled on the deployed
 
 #### Populate scratchpad
 
-You can use a data source to populate a scratchpad with a dataset, allowing you to build complex APIs and pipelines within VS Code and kdb Insights Enterprise. 
+You can use a data source to populate a scratchpad with a dataset, allowing you to build complex APIs and pipelines within VS Code and kdb Insights Enterprise.
 
 To do this:
 
 1. Create a data source and execute it using the 'Populate Scratchpad' button.
-    The scratchpad is populated.
-   
+   The scratchpad is populated.
 1. At the prompt, provide a variable to populate your own scratchpad instance with the data.
 
 1. Return to VS Code and execute q code against the data in your scratchpad.
 
 ![Populate Scratchpad](https://code.kx.com/img/vscode/populate-scratchpad.png)
 
-
 ## View results
 
 All query executions happen remotely from the kdb VS Code extension either against a running q process or against an instance of kdb Insights Enterprise. The results, successful or otherwise, are returned to VS Code as:
 
 - An output view
 
-    The output view displays results as they are received by the kdb VS Code extension. It includes the query executed, a timestamp and the results.
+  The output view displays results as they are received by the kdb VS Code extension. It includes the query executed, a timestamp and the results.
 
-    ![Output view](https://code.kx.com/img/vscode/output-results.png)
+  ![Output view](https://code.kx.com/img/vscode/output-results.png)
 
-    **Note:** You can enable/disable auto-scrolling in the VS Code settings. This setting determines whether the output view scrolls to the latest results.
+  **Note:** You can enable/disable auto-scrolling in the VS Code settings. This setting determines whether the output view scrolls to the latest results.
 
-    ![Output autoscrolling](https://code.kx.com/img/vscode/auto-scrolling.png)
+  ![Output autoscrolling](https://code.kx.com/img/vscode/auto-scrolling.png)
 
-- A kdb results view
+  **Note** You can hide or show the full details in the console output. Go to settings of the vscode, search for kdb, check the option "Hide Detailed Console Query Output" (this option is checked by default)
 
-    Results are displayed under the kdb results view, which shows the returned data in a table.
+  ![Hide Detailed Console Query Output](https://code.kx.com/img/vscode/hide-detailed-console-query.png)
 
-    ![kdb results view](https://code.kx.com/img/vscode/kdbview-results.png)
+- A kdb results view
 
+  Results are displayed under the kdb results view, which shows the returned data in a table.
+
+  ![kdb results view](https://code.kx.com/img/vscode/kdbview-results.png)
 
 ## Settings
 
-To update kdb VS Code settings, search for `kdb` from _Preferences_ > _Settings_, or right-click the settings icon in kdb VS Code marketplace panel and choose _Extension Settings_. 
+To update kdb VS Code settings, search for `kdb` from _Preferences_ > _Settings_, or right-click the settings icon in kdb VS Code marketplace panel and choose _Extension Settings_.
 
-Item                                                       | Action
----------------------------------------------------------- | -------
-Hide notification of installation path after first install | yes/no; default `no`
-Hide subscription to newsletter after first install        | yes/no; default `no`
-Insights Enterprise Connections for Explorer                                      | [edit JSON settings](#insights-enterprise-connections-for-explorer)
-QHOME directory for q runtime                              | Display location path of q installation
-Servers                                                    | [edit JSON settings](#servers)
+| Item                                                       | Action                                                              |
+| ---------------------------------------------------------- | ------------------------------------------------------------------- |
+| Hide notification of installation path after first install | yes/no; default `no`                                                |
+| Hide subscription to newsletter after first install        | yes/no; default `no`                                                |
+| Insights Enterprise Connections for Explorer               | [edit JSON settings](#insights-enterprise-connections-for-explorer) |
+| QHOME directory for q runtime                              | Display location path of q installation                             |
+| Servers                                                    | [edit JSON settings](#servers)                                      |
 
 ### Insights Enterprise Connections for Explorer
 
@@ -373,7 +361,7 @@ Servers                                                    | [edit JSON settings
     "kdb.qHomeDirectory": "C:\\qhomedirectory",
     "kdb.hideInstallationNotification": true,
     "kdb.servers": {
-    
+
         "23XdJyFk7hXb35Z3yw2vP87HOHFIfy0PDoo5+/G1o7A=": {
             "auth": true,
             "serverName": "127.0.0.1",
@@ -393,15 +381,13 @@ Servers                                                    | [edit JSON settings
 }
 ```
 
-
 ## Shortcuts
 
-| Key | Action |
-| - | - |
-| F12 | Go to definition |
-| Shift + F12 | Go to references |
-| Cmd/Ctrl + Shift + F12 | Find all references |
-| Ctrl + Q | Execute current selection |
-| Ctrl + Shift + Q | Execute entire file |
-| Ctrl + Shift + R | Run q file in new q instance |
-
+| Key                    | Action                       |
+| ---------------------- | ---------------------------- |
+| F12                    | Go to definition             |
+| Shift + F12            | Go to references             |
+| Cmd/Ctrl + Shift + F12 | Find all references          |
+| Ctrl + Q               | Execute current selection    |
+| Ctrl + Shift + Q       | Execute entire file          |
+| Ctrl + Shift + R       | Run q file in new q instance |

From 2949853690781378d287e202c63e928e0d224f9f Mon Sep 17 00:00:00 2001
From: fallond <dfallon@kx.com>
Date: Tue, 24 Oct 2023 15:00:39 +0100
Subject: [PATCH 2/3] Update README.md

---
 README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 12a12da3..f6e97dd0 100644
--- a/README.md
+++ b/README.md
@@ -115,20 +115,20 @@ The kdb VS Code extension allows you to connect VS Code to a q process; this can
 
 - I want to learn more about [setting a q port](https://code.kx.com/q/basics/ipc/)
 
-**Step 7**: If authentication is required, define the _username_, then the _password_; clicking Enter with these inputs blank skips these steps.
-
-**Step 8**: An option to enable TLS encryption is offered; the default is _false_.
-
-- I want to learn more [about TLS encryption](https://code.kx.com/q/kb/ssl/).
-
 Upon completion, the localhost connection appears under _KX:CONNECTIONS_ in the left hand panel.
 
 ![localkdbconnection](https://code.kx.com/img/vscode/localkdbconnection.jpg)
 
-**Step 9**: Right-click the connection to _connect kdb server_. Ensure the q process is running.
+**Step 7**: Right-click the connection to _connect kdb server_. Ensure the q process is running.
 
 ![localkdbconnection](https://code.kx.com/img/vscode/connectserver.jpg)
 
+If authentication is required, from the connection dropdown menu define the _username_, then the _password_.
+
+An option to enable TLS encryption is offered; the default is _false_.
+
+- I want to learn more [about TLS encryption](https://code.kx.com/q/kb/ssl/).
+
 ### Managed q session
 
 This runs a q session using the existing kdb installed as part of the kdb VS Code extension.

From b3f206e8cff92f3f85916ccb40dc75b2f8fe17fa Mon Sep 17 00:00:00 2001
From: fallond <dfallon@kx.com>
Date: Tue, 24 Oct 2023 15:04:59 +0100
Subject: [PATCH 3/3] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index f6e97dd0..9dbb9ea1 100644
--- a/README.md
+++ b/README.md
@@ -123,9 +123,9 @@ Upon completion, the localhost connection appears under _KX:CONNECTIONS_ in the
 
 ![localkdbconnection](https://code.kx.com/img/vscode/connectserver.jpg)
 
-If authentication is required, from the connection dropdown menu define the _username_, then the _password_.
+If authentication is required to access the connection, from the connection dropdown menu, add the required _username_ and the _password_, clicking Enter to move between the two.
 
-An option to enable TLS encryption is offered; the default is _false_.
+From the connection dropdown menu there is also an option to enable TLS encryption; the default is _false_.
 
 - I want to learn more [about TLS encryption](https://code.kx.com/q/kb/ssl/).