Fix spelling

Author: richelbilderbeek

docs/day2/IDEs.rst

@@ -1008,7 +1008,7 @@ Main panes and useful panels
 
    **For Jupyter Notebooks (and a much safer option)** 🧪
 
-   * You need to start the server on the HPC resource first, preferrably on a compute node. 
+   * You need to start the server on the HPC resource first, preferably on a compute node. 
    * Copy the jupyter server URL which goes something like ``http://s193.uppmax.uu.se:8888/tree?token=xxx`` (where s193 is Snowy node. Other HPCs will have similar URLs), click on ``Select Kernel`` on VSCode and select ``Existing Jupyter Server``. Past the URL here and confirm your choice.
    * This only works if you have the jupyter extension installed on your local VSCode.
    * The application will automatically perform port forwarding to your local machine from the compute nodes over certain ports. Check the Terminal->Ports tab to see the correct url to open in your browser.
@@ -1032,7 +1032,7 @@ Exercises
    * Create a Virtual env using your faviroute package manager and install the packages.  
    * For an extra challenge: Run the same code in .ipynb format in your IDE. This requires you to install jupyter notebook in your virtual environment.
 
-   .. admonition:: Solving linear system of equations and optimiztion task using Scipy
+   .. admonition:: Solving linear system of equations and optimization task using Scipy
       :class: dropdown
 
       Install ``Scipy`` for the following example.

docs/day2/IDEs_cmd.rst

@@ -638,7 +638,7 @@ VS Code can be downloaded and installed on your local machine from the `VS Code
 However, VS Code is best used on your local machine, as it is a resource-intensive application that can slow down the ThinLinc interface. The VS Code Server can be installed on all the HPCs that give your the ability to run your code on the HPCs but edit it on your local machine.
 Similarly, you can also install your faviroute extensions on the HPCs and use them on your local machine. Care should be taken while assigning the correct installation directories for the extensions because otherwise they get installed in home directory and eat up all the space.
 
-**Installed on HPC clusters**
+**Installed on HPC **
 
 - Tetralith: ``VSCode/latest-bdist``
     - Start with ``code``
@@ -649,7 +649,7 @@ Similarly, you can also install your faviroute extensions on the HPCs and use th
 - Cosmos: system-installed (no module needed)
     - Start with ``code``
 
-For the HPC slusters below you need to connect from a local VSCode client (works also for all clusters)
+For the HPC slusters below you need to connect from a local VSCode client (works also for all )
 
 - Dardel
 - Kebnekaise
@@ -665,7 +665,7 @@ Install VS Code on your local machine and follow the steps below to connect to t
 
    .. figure:: ../img/vscode_remote_tunnels_before_install.png
 
-   Since most clusters now has added the TOTP feature you have to make another setting as well.  
+   Since most  now has added the TOTP feature you have to make another setting as well.  
 
    - Go to settings (the lower-left corner wheel):
 

docs/day2/interactive.rst

@@ -75,7 +75,7 @@ Any longer, resource-intensive, or parallel jobs must be run through a **batch s
 
    - Demanding work (CPU or Memory intensive) should be done on the compute nodes.
    - If you need live interaction you should start an "interactive session"
-   - On Cosmos (LUNARC), Dardel (PDC), Alvis (C3SE), and Kebnekaise (HPC2N) it can be done graphically with the Desktop-On-Demand tool ``GfxLauncher`` or portal.
+   - On Cosmos (LUNARC), Dardel (PDC), Alvis (C3SE), and Kebnekaise (HPC2N) it can be done ly with the Desktop-On-Demand tool ``GfxLauncher`` or portal.
    - Otherwise the terminal approach will work in all centers.
 
 The different way HPC2N, UPPMAX, LUNARC, NSC, PDC, and C3SE provide for an interactive session

docs/day2/interactive_old.rst

@@ -75,7 +75,7 @@ Any longer, resource-intensive, or parallel jobs must be run through a **batch s
 
    - Demanding work (CPU or Memory intensive) should be done on the compute nodes.
    - If you need live interaction you should start an "interactive session"
-   - On Cosmos (LUNARC), Dardel (PDC), Alvis (C3SE), and Kebnekaise (HPC2N) it can be done graphically with the Desktop-On-Demand tool ``GfxLauncher`` or portal.
+   - On Cosmos (LUNARC), Dardel (PDC), Alvis (C3SE), and Kebnekaise (HPC2N) it can be done ly with the Desktop-On-Demand tool ``GfxLauncher`` or portal.
    - Otherwise the terminal approach will work in all centers.
 
 The different way HPC2N, UPPMAX, LUNARC, NSC, PDC, and C3SE provide for an interactive session
@@ -689,7 +689,7 @@ Conclusion
 
 
     At centres that have OpenOnDemand installed, you do not have to submit a batch job, but can run directly on the already allocated resources (see interactive jobs).
-        OpenOnDemand is a good option for interactive tasks, graphical applications/visualization, and simpler job submittions. It can also be more user-friendly.
+        OpenOnDemand is a good option for interactive tasks,  applications/visualization, and simpler job submissions. It can also be more user-friendly.
         Regardless, there are many situations where submitting a batch job is the best option instead, including when you want to run jobs that need many resources (time, memory, multiple cores, multiple GPUs) or when you run multiple jobs concurrently or in a specified succession, without need for manual intervention. Batch jobs are often also preferred for automation (scripts) and reproducibility. Many types of application software fall into this category.
     At centres that have ThinLinc you can usually submit MATLAB jobs to compute resources from within MATLAB.
 

docs/day2/may2024/install_packages.rst

@@ -29,7 +29,7 @@ As an example, maybe you have been using TensorFlow 1.x.x for your project and n
 - Isolated environments lets you create separate workspaces for different versions of Python and/or different versions of packages.
 - You can activate and deactivate them one at a time, and work as if the other workspace does not exist.
 
-There are different tools for creating an isolated environement, but they all have some things in common.
+There are different tools for creating an isolated environment, but they all have some things in common.
 
 At UPPMAX, HPC2N, and LUNARC (and most other Swedish HPC centers that use modules) the workflow is:
 

docs/day2/ondemand-desktop.rst

@@ -315,7 +315,7 @@ Most settings are the same, with exception of the "Resource" or "Node Type"/"Cor
 
 
 - At centres that have OpenOnDemand installed, you do not have to submit a batch job, but can run directly on the already allocated resources
-- OpenOnDemand is a good option for interactive tasks, graphical applications/visualization, and simpler job submittions. It can also be more user-friendly.
+- OpenOnDemand is a good option for interactive tasks, graphical applications/visualization, and simpler job submissions. It can also be more user-friendly.
 - Regardless, there are many situations where submitting a batch job is the best option instead, including when you want to run jobs that need many resources (time, memory, multiple cores, multiple GPUs) or when you run multiple jobs concurrently or in a specified succession, without need for manual intervention. Batch jobs are often also preferred for automation (scripts) and reproducibility. Many types of application software fall into this category.
 - At centres that have ThinLinc you can usually submit MATLAB jobs to compute resources from within MATLAB.