Run user tutorials through Grammarly extension

marcelldls · marcelldls · commit d188d17bd65b · 2023-11-14T10:51:42.000Z
diff --git a/docs/user/tutorials/create_beamline.rst b/docs/user/tutorials/create_beamline.rst
@@ -60,7 +60,7 @@ You will also need to setup ssh keys to authenticate to github from git. See
 Create a New Repository
 -----------------------
 
-Here we will copy the beamline template repository and change it's name to bl01t.
+Here we will copy the beamline template repository and change its name to bl01t.
 We will then step through the changes that are required to make it your own.
 
 NOTE: for these tutorials we will use your personal GitHub Account to
@@ -118,7 +118,7 @@ Environment.sh
 ~~~~~~~~~~~~~~
 
 Environment.sh is a bash script that is sourced by a beamline user or developer
-in order to setup their environment to work with the beamline.
+in order to set up their environment to work with the beamline.
 
 The command line tool ``ec`` uses the environment configured by this script
 to determine where to deploy IOCS and where to find container images etc.
diff --git a/docs/user/tutorials/create_ioc.rst b/docs/user/tutorials/create_ioc.rst
@@ -277,7 +277,7 @@ Viewing IOC output
 ~~~~~~~~~~~~~~~~~~
 
 Our detector output is available over PVAccess since we added the PVA plugin.
-We can view it using the ``c2dv`` tool. Theses commands will install ``c2dv``
+We can view it using the ``c2dv`` tool. These commands will install ``c2dv``
 and launch it to view the IOC output:
 
 .. code-block:: bash
@@ -392,7 +392,7 @@ docker if that is what you are using):
 
 Your IOC Instance will now be using the raw startup script and database. But
 should behave exactly the same as before. You are free to experiment with
-changes in the  startup script and substitution file and re-deploy the IOC.
+changes in the startup script and substitution file and re-deploy the IOC.
 
 .. note::
 
diff --git a/docs/user/tutorials/debug_generic_ioc.rst b/docs/user/tutorials/debug_generic_ioc.rst
@@ -6,7 +6,7 @@ Debugging Generic IOC Builds
     This tutorial is out of date and will be updated soon.
 
 This tutorial is a continuation of `generic_ioc`. Here we will look into
-debugging failed builds and fix the issue we saw in the  previous tutorial.
+debugging failed builds and fix the issue we saw in the previous tutorial.
 
 This also comes under the category of type 2. change from the list
 at `ioc_change_types`.
diff --git a/docs/user/tutorials/deploy_example.rst b/docs/user/tutorials/deploy_example.rst
@@ -69,7 +69,7 @@ where indicated):
     source bl01t
 
 Once you have done this and logged out and back in again to pick up your new
-profile you should be able enable the ``bl01t`` environment as follows:
+profile you should be able to enable the ``bl01t`` environment as follows:
 
 .. code-block:: bash
 
@@ -97,7 +97,7 @@ IOC Instance.
 
 The following command will deploy the example IOC instance to your local
 machine (unless you have skipped ahead and set up your Kubernetes config
-in which case the same command  will deploy to your Kubernetes cluster).
+in which case the same command will deploy to your Kubernetes cluster).
 
 .. code-block:: bash
 
@@ -158,7 +158,7 @@ Managing the Example IOC Instance
 Starting and Stopping IOCs
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To stop / start  the example IOC try the following commands. Note that
+To stop / start the example IOC try the following commands. Note that
 ``ec ps -a`` shows you all IOCs including stopped ones.
 
 .. code-block:: bash
diff --git a/docs/user/tutorials/dev_container.rst b/docs/user/tutorials/dev_container.rst
@@ -217,7 +217,7 @@ multiple peer projects.
 
 In VSCode click the ``File`` menu and select ``Add Folder to Workspace``.
 Navigate to ``/repos`` and you will see all the peers of your ``ioc-adsimdetector``
-folder (see `container-layout` below) . Choose the ``bl01t`` folder and add it to the
+folder (see `container-layout` below). Choose the ``bl01t`` folder and add it to the
 workspace - you may see an error but if so clicking "reload window" will
 clear it.
 
@@ -230,8 +230,8 @@ Also take this opportunity to add the folder ``/epics`` to the workspace.
   and git will complain about ownership. You can cancel out of these errors
   as you should not edit project folders inside of ``/epics`` - they were
   built by the container and should be considered immutable. We will learn
-  how to work on support modules in later tuorials. This error should only
-  be seen on first launch. podman users will have no such problem becuase they
+  how to work on support modules in later tutorials. This error should only
+  be seen on first launch. podman users will have no such problem because they
   will be root inside the container and root build the container.
 
 You can now easily browse around the ``/epics`` folder and see all the
diff --git a/docs/user/tutorials/generic_ioc.rst b/docs/user/tutorials/generic_ioc.rst
@@ -11,7 +11,7 @@ test our changes locally before deploying it.
 This is a type 2. change from the list at `ioc_change_types`.
 
 The example IOC used ADSimDetector, we will make a similar IOC that uses
-ADUrl to get images from a web cam.
+ADUrl to get images from a webcam.
 
 Create a New Generic IOC project
 --------------------------------
@@ -49,7 +49,7 @@ using an ``ec`` command.
     From the VSCode menus: File->Add Folder to Workspace
     then select the folder ioc-adurl
 
-#.  Push the repo back to a the new repo on github
+#.  Push the repo back to a new repo on github
 
     .. code-block:: bash
 
diff --git a/docs/user/tutorials/ioc_changes1.rst b/docs/user/tutorials/ioc_changes1.rst
@@ -128,7 +128,7 @@ into the Generic IOC (ioc-adsimdetector). Each support module has an
 ``ibek`` *support YAML* file that contributes to the schema.
 
 The *Support yaml* files are in the folder ``/epics/ibek`` inside of the
-container. They were placed their during the compilation of the support
+container. They were placed there during the compilation of the support
 modules at Generic IOC build time.
 
 It can be instructive to look at these files to see what entities are available
diff --git a/docs/user/tutorials/setup_workstation.rst b/docs/user/tutorials/setup_workstation.rst
@@ -1,7 +1,7 @@
-Setup a Developer Workstation
+Set up a Developer Workstation
 =============================
 
-This page will guide you through the steps to setup a developer workstation
+This page will guide you through the steps to set up a developer workstation
 in readiness for the remaining tutorials.
 The tools you need to install are:
 
@@ -45,14 +45,14 @@ Setup VSCode
 
 .. Note::
 
-    **DLS Users**:  You can access VSCode with ``module load vscode``.
+    **DLS Users**: You can access VSCode with ``module load vscode``.
 
 First download and install Visual Studio Code.
 
 - `Download Visual Studio Code`_
 - `Setup Visual Studio Code`_
 
-VSCode has an huge library of extensions. The following list of extensions are
+VSCode has a huge library of extensions. The following list of extensions are
 useful for working with epics-containers. You will need to install the *Required*
 extensions before proceeding to the next tutorial. See the links for instructions
 on how to do this.
@@ -82,7 +82,7 @@ Setup Docker or Podman
     **DLS Users**: RHEL 8 Workstations at DLS have podman 4.4.1 installed by default.
     RHEL 7 Workstations are not supported.
 
-Next install docker or podman as the your container platform. epics-containers
+Next install docker or podman as your container platform. epics-containers
 has been tested with podman 4.4.1 on RedHat 8, and Docker 24.0.5 on
 for Ubuntu 22.04.
 
@@ -135,7 +135,7 @@ but you can choose any folder.
     python -m pip install --upgrade pip
 
 Note that each time you open a new shell you will need to activate the virtual
-environment again. (Or place it's bin folder in your path permanently).
+environment again. (Or place its bin folder in your path permanently).
 
 
 .. _ec:
