Small edits on recent updates

Author: Greg Van Liew

api/advanced-topics/remote-extensions.md

@@ -396,7 +396,7 @@ export async function activate(context: vscode.ExtensionContext) {
     vscode.window.registerUriHandler({
         handleUri(uri: vscode.Uri): vscode.ProviderResult<void> {
 
-            // Add your code for what to do when the auth completes here.
+            // Add your code for what to do when the authentication completes here.
             if (uri.path === '/auth-complete') {
                 vscode.window.showInformationMessage('Sign in successful!');
             }
@@ -407,7 +407,7 @@ export async function activate(context: vscode.ExtensionContext) {
     // Register a sign in command
     context.subscriptions.push(vscode.commands.registerCommand(`${extensionId}.signin`, async () => {
 
-        // Get an externally addressable callback URI for the handler that the auth provider can use
+        // Get an externally addressable callback URI for the handler that the authentication provider can use
         const callbackUri = await vscode.env.asExternalUri(vscode.Uri.parse(`${vscode.env.uriScheme}://${extensionId}/auth-complete`));
 
         // Add your code to integrate with an authentication provider here - we'll fake it.

docs/remote/containers-advanced.md

@@ -647,7 +647,7 @@ Then, add the following to `settings.json` (replacing values as appropriate):
 
 After restarting VS Code (or reloading the window), you will now be able to [attach to any running container](/docs/remote/containers.md#attaching-to-running-containers) on the remote host. You can also [use specialized, local `devcontainer.json` files to create / connect to a remote dev container](#converting-an-existing-or-predefined-devcontainerjson).
 
-> **Tip:** If this is not working for you but you are able to connect to the host using SSH from the command line, be sure you have the [SSH agent running with your auth key](/docs/remote/containers.md#using-ssh-keys). If all else fails, you can use [a SSH tunnel as a fallback](/docs/remote/troubleshooting.md#using-an-ssh-tunnel-to-connect-to-a-remote-docker-host) instead.
+> **Tip:** If this is not working for you but you are able to connect to the host using SSH from the command line, be sure you have the [SSH agent running with your authentication key](/docs/remote/containers.md#using-ssh-keys). If all else fails, you can use [an SSH tunnel as a fallback](/docs/remote/troubleshooting.md#using-an-ssh-tunnel-to-connect-to-a-remote-docker-host) instead.
 
 **Using the TCP protocol**
 

docs/remote/troubleshooting.md

@@ -190,7 +190,7 @@ If you are connecting to an SSH remote host and are either:
 - using password authentication,
 - using an SSH key with a passphrase when the [SSH Agent](#setting-up-the-ssh-agent) is not running or accessible,
 
-...VS Code should automatically prompt you to enter needed information. If you do not see the prompt, enable the `remote.SSH.showLoginTerminal` [setting](/docs/getstarted/settings.md) in VS Code. This setting displays the terminal whenever VS Code runs an SSH command. You can then enter your auth code, password, or passphrase when the terminal appears.
+...VS Code should automatically prompt you to enter needed information. If you do not see the prompt, enable the `remote.SSH.showLoginTerminal` [setting](/docs/getstarted/settings.md) in VS Code. This setting displays the terminal whenever VS Code runs an SSH command. You can then enter your authentication code, password, or passphrase when the terminal appears.
 
 If you are on macOS and Linux and want to reduce how often you have to enter a password or token, you can enable the `ControlMaster` feature on your **local machine** so that OpenSSH runs multiple SSH sessions over a single connection.
 

remote-release-notes/v1_37.md

@@ -58,7 +58,7 @@ If you lose your internet connection during a remote session, VS Code has to rec
 
 ### Improved password authentication
 
-If you are using password-based authentication for your SSH remote, then currently you have to enter your password twice for each window, each reconnection, and again if you want to forward a port. We are experimenting with a new way to set up the SSH connection that will only require one password when the window opens, and no extra password entry to forward a port. To try it out, set `"remote.SSH.enableDynamicForwarding": true` and report any issues that you see. This mode is also a little faster connecting, even if you aren't using password-based auth.
+If you are using password-based authentication for your SSH remote, then currently you have to enter your password twice for each window, each reconnection, and again if you want to forward a port. We are experimenting with a new way to set up the SSH connection that will only require one password when the window opens, and no extra password entry to forward a port. To try it out, set `"remote.SSH.enableDynamicForwarding": true` and report any issues that you see. This mode is also a little faster connecting, even if you aren't using password-based authentication.
 
 And we still recommend [setting up key-based authentication](https://code.visualstudio.com/docs/remote/troubleshooting#_configuring-key-based-authentication) for the best experience.
 

remote-release-notes/v1_38.md

@@ -72,4 +72,4 @@ We are holding this back from the Stable release to allow for extension authors
 
 ### Experimental features turned on by default
 
-Last month we added experimental support for SSH's `ForwardAgent` option and "dynamic forwarding", which provides a better experience when using password auth. Those features are now enabled by default.
+Last month we added experimental support for SSH's `ForwardAgent` option and "dynamic forwarding", which provides a better experience when using password authentication. Those features are now enabled by default.