Small edits

docs/datascience/notebooks-web.md

@@ -87,22 +87,22 @@ Since VS Code for the Web runs entirely in your web browser, there are some limi
 
 As with VS Code Desktop, you can easily continue your work from VS Code for the Web ([https://vscode.dev](https://vscode.dev) or [https://github.dev](https://github.dev)) on Codespaces. When you choose to **Continue Working On** in a new codespace, your uncommitted changes will travel with you. To do so:
 
-1. Open the Command Palette (`kb(workbench.action.showCommands)`) and select **Continue Working On...**
-2. Select **Create New Codespace**
+1. Open the Command Palette (`kb(workbench.action.showCommands)`) and select **Continue Working On...**.
+2. Select **Create New Codespace**.
 
    ![Continue working on](images/notebooks-web/continue-working-on-codespaces.png)
 
-3. Follow the prompts to store your working changes in the cloud and to sign into Codespaces
-4. Select the instance type for your Codespace (i.e., number of cores, RAM, and storage)
+3. Follow the prompts to store your working changes in the cloud and to sign into Codespaces.
+4. Select the instance type for your codespace (number of cores, RAM, and storage).
 
-You can also manually commit your changes and create a Codespace through the **Remote Explorer**:
+You can also manually commit your changes and create a codespace through the **Remote Explorer**:
 
 1. Sign into Codespaces by opening the Command Palette (`kb(workbench.action.showCommands)`) and selecting **Codespaces: Sign in**.
 2. Navigate to the **Remote Explorer** view from the Activity bar.
 
     ![Remote explorer tab](images/notebooks-web/remote-explorer-tab.png)
 
-From the **Remote Explorer** view, you can either connect to an existing Codespace or create a new one. This will open up a new window for you to continue working on your project on Codespaces.
+From the **Remote Explorer** view, you can either connect to an existing codespace or create a new one. This will open up a new window for you to continue working on your project on Codespaces.
 
 ## Questions or feedback
 

docs/python/python-tutorial.md

@@ -252,8 +252,8 @@ To install the `matplotlib` package (which also installs `numpy` as a dependency
 A best practice among Python developers is to avoid installing packages into a global interpreter environment. You instead use a project-specific `virtual environment` that contains a copy of a global interpreter. Once you activate that environment, any packages you then install are isolated from other environments. Such isolation reduces many complications that can arise from conflicting package versions. To create a *virtual environment* and install the required packages, enter the following commands as appropriate for your operating system:
 
 > **Note**: For additional information about virtual environments, see [Environments](/docs/python/environments.md#creating-environments).
-
-1. Create a Virtual Environment using the Create Environment Command
+v
+1. Create a virtual environment using the Create Environment command
 
    From within VS Code, you can create non-global environments, using Venv or Anaconda, by opening the Command Palette (`kb(workbench.action.showCommands)`), start typing the **Python: Create Environment** command to search, and then select the command. You can also trigger the **Python: Create Environment** command through the Getting Started with Python page.
 

docs/terminal/appearance.md

@@ -160,4 +160,4 @@ The [minimum contrast ratio feature](#minimum-contrast-ratio) can cause colors t
 "terminal.integrated.minimumContrastRatio": 1
 ```
 
-Background on why this is the default is explained in [vscode#146406](https://github.com/microsoft/vscode/issues/146406#issuecomment-1084825473).
+Background on why this is the default is explained in [vscode#146406](https://github.com/microsoft/vscode/issues/146406#issuecomment-1084825473).

docs/terminal/profiles.md

@@ -116,7 +116,7 @@ By default, the task/debug features will use the default profile. This may not b
 
 ## Unsafe profile detection
 
-Certain shells are installed in unsafe paths by default, like a path that could be written to by another user on a Windows environment. VS Code will still detect these but not expose them as a proper profile until they have been explicitly configured via the **Terminal: Select Default Profile** command. When configuring an unsafe profile there will be a warning before it's added:
+Certain shells are installed in unsafe paths by default, like a path that could be written to by another user on a Windows environment. VS Code will still detect these but not expose them as a proper profile until they have been explicitly configured via the **Terminal: Select Default Profile** command. When configuring an unsafe profile, there will be a warning before it's added:
 
 ![Shells with unsafe paths like c:\msys64 will show a warning before you can use the detected profile](images/profiles/unsafe-profile-warning.png)