Skip to content

Commit 1ad1d8b

Browse files
committed
acrolinx
1 parent 06dd14f commit 1ad1d8b

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/machine-learning/how-to-access-terminal.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,10 @@ To access the terminal:
3737
:::image type="content" source="media/how-to-use-terminal/open-terminal-window.png" alt-text="Open terminal window":::
3838

3939
1. When a compute instance is running, the terminal window for that compute instance appears.
40-
1. When no compute instance is running, use the **Compute** section on the right to start or create a compute instance.
40+
1. When no compute instance is running, use the **Compute** section to start or create a compute instance.
4141
:::image type="content" source="media/how-to-use-terminal/start-or-create-compute.png" alt-text="Start or create a compute instance":::
4242

43-
In addition to the steps above, you can also access the terminal from:
43+
In addition to the previous steps, you can also access the terminal from:
4444

4545
* RStudio or Posit Workbench (formerly RStudio Workbench) (See [Add custom applications such as RStudio or Posit Workbench)](how-to-create-compute-instance.md?tabs=python#add-custom-applications-such-as-rstudio-or-posit-workbench)): Select the **Terminal** tab on top left.
4646
* Jupyter Lab: Select the **Terminal** tile under the **Other** heading in the Launcher tab.
@@ -55,7 +55,7 @@ In addition to the steps above, you can also access the terminal from:
5555
5656
## <a name=git></a> Use files from Git and version files
5757

58-
Access all Git operations from the terminal. All Git files and folders will be stored in your workspace file system. This storage allows you to use these files from any compute instance in your workspace.
58+
Access all Git operations from the terminal. All Git files and folders are stored in your workspace file system. This storage allows you to use these files from any compute instance in your workspace.
5959

6060
> [!NOTE]
6161
> Add your files and folders anywhere under the **~/cloudfiles/code/Users** folder so they will be visible in all your Jupyter environments.
@@ -64,7 +64,7 @@ To integrate Git with your Azure Machine Learning workspace, see [Git integrati
6464

6565
## Install packages
6666

67-
Install packages from a terminal window. Install packages into the kernel that you want to use to run your notebooks. The default kernel is **python310-sdkv2**.
67+
Install packages from a terminal window. Install packages into the kernel that you want to use to run your notebooks. The default kernel is **python310-sdkv2**.
6868

6969
Or you can install packages directly in Jupyter Notebook, RStudio, or Posit Workbench (formerly RStudio Workbench):
7070

@@ -81,13 +81,13 @@ Or you can install packages directly in Jupyter Notebook, RStudio, or Posit Work
8181
8282
To add a new Jupyter kernel to the compute instance:
8383

84-
1. Use the terminal window to create a new environment. For example, the code below creates `newenv`:
84+
1. Use the terminal window to create a new environment. For example, the following command creates `newenv`:
8585

8686
```shell
8787
conda create --name newenv
8888
```
8989

90-
1. Activate the environment. For example, after creating `newenv`:
90+
1. Activate the environment. For example, after creating `newenv`:
9191

9292
```shell
9393
conda activate newenv
@@ -105,13 +105,13 @@ Any of the [available Jupyter Kernels](https://github.com/jupyter/jupyter/wiki/J
105105

106106
To add a new R kernel to the compute instance:
107107

108-
1. Use the terminal window to create a new environment. For example, the code below creates `r_env`:
108+
1. Use the terminal window to create a new environment. For example, the following command creates `r_env`:
109109

110110
```shell
111111
conda create -n r_env r-essentials r-base
112112
```
113113

114-
1. Activate the environment. For example, after creating `r_env`:
114+
1. Activate the environment. For example, after creating `r_env`:
115115

116116
```shell
117117
conda activate r_env
@@ -135,7 +135,7 @@ To add a new R kernel to the compute instance:
135135
q()
136136
```
137137
138-
It will take a few minutes before the new R kernel is ready to use. If you get an error saying it is invalid, wait and then try again.
138+
It takes a few minutes before the new R kernel is ready to use. If you get an error saying it's invalid, wait and then try again.
139139
140140
For more information about conda, see [Using R language with Anaconda](https://docs.anaconda.com/free/anaconda/packages/using-r-language/). For more information about IRkernel, see [Native R kernel for Jupyter](https://cran.r-project.org/web/packages/IRkernel/readme/README.html).
141141
@@ -144,7 +144,7 @@ For more information about conda, see [Using R language with Anaconda](https://d
144144
> [!WARNING]
145145
> While customizing the compute instance, make sure you do not delete conda environments or jupyter kernels that you didn't create.
146146
147-
To remove an added Jupyter kernel from the compute instance, you must remove the kernelspec, and (optionally) the conda environment. You can also choose to keep the conda environment. You must remove the kernelspec, or your kernel will still be selectable and cause unexpected behavior.
147+
To remove an added Jupyter kernel from the compute instance, you must remove the kernelspec, and (optionally) the conda environment. You can also choose to keep the conda environment. You must remove the kernelspec, or your kernel is still selectable and cause unexpected behavior.
148148
149149
To remove the kernelspec:
150150
@@ -174,11 +174,11 @@ To also remove the conda environment:
174174
conda env remove -n ENV_NAME
175175
```
176176
177-
Upon refresh, the kernel list in your notebooks view should reflect the changes you have made.
177+
Upon refresh, the kernel list in your notebooks view should reflect the changes you made.
178178
179179
## Manage terminal sessions
180180
181-
Terminal sessions can stay active if terminal tabs are not properly closed. Too many active terminal sessions can impact the performance of your compute instance.
181+
Terminal sessions can stay active if terminal tabs aren't properly closed. Too many active terminal sessions can impact the performance of your compute instance.
182182
183183
Select **Manage active sessions** in the terminal toolbar to see a list of all active terminal sessions and shut down the sessions you no longer need.
184184

0 commit comments

Comments
 (0)