Update remote-visualization.md PROOFREAD

I haven't proofread the code
line 208; do you mean 'resolution' rather than 'responsibility'?

docs.it4i/anselm/remote-visualization.md

@@ -2,11 +2,11 @@
 
 ## Introduction
 
-The goal of this service is to provide the users a GPU accelerated use of OpenGL applications, especially for pre- and post- processing work, where not only the GPU performance is needed but also fast access to the shared file systems of the cluster and a reasonable amount of RAM.
+The goal of this service is to provide users with GPU accelerated use of OpenGL applications, especially for pre- and post- processing work, where not only GPU performance is needed but also fast access to the shared file systems of the cluster and a reasonable amount of RAM.
 
-The service is based on integration of open source tools VirtualGL and TurboVNC together with the cluster's job scheduler PBS Professional.
+The service is based on integration of the open source tools VirtualGL and TurboVNC together with the cluster's job scheduler PBS Professional.
 
-Currently two compute nodes are dedicated for this service with following configuration for each node:
+Currently there are two dedicated compute nodes for this service with the following configuration for each node:
 
 | [**Visualization node configuration**](compute-nodes/) |                                         |
 | ------------------------------------------------------ | --------------------------------------- |
@@ -27,7 +27,7 @@ Currently two compute nodes are dedicated for this service with following config
 
 ### Setup and Start Your Own TurboVNC Server
 
-TurboVNC is designed and implemented for cooperation with VirtualGL and available for free for all major platforms. For more information and download, please refer to: <http://sourceforge.net/projects/turbovnc/>
+TurboVNC is designed and implemented for cooperation with VirtualGL and is available for free for all major platforms. For more information and download, please refer to: <http://sourceforge.net/projects/turbovnc/>
 
 **Always use TurboVNC on both sides** (server and client) **don't mix TurboVNC and other VNC implementations** (TightVNC, TigerVNC, ...) as the VNC protocol implementation may slightly differ and diminish your user experience by introducing picture artifacts, etc.
 
@@ -39,12 +39,12 @@ Please [follow the documentation](shell-and-data-access/).
 
 #### 2. Run Your Own Instance of TurboVNC Server
 
-To have the OpenGL acceleration, **24 bit color depth must be used**. Otherwise only the geometry (desktop size) definition is needed.
+To have OpenGL acceleration, **24 bit color depth must be used**. Otherwise only the geometry (desktop size) definition is needed.
 
 !!! hint
-    At first VNC server run you need to define a password.
+    The first time the VNC server is run you need to define a password.
 
-This example defines desktop with dimensions 1200x700 pixels and 24 bit color depth.
+This example defines a desktop with the dimensions of 1200x700 pixels and 24 bit color depth.
 
 ```console
 $ module load turbovnc/1.2.2
@@ -69,7 +69,7 @@ X DISPLAY # PROCESS ID
 
 In this example the VNC server runs on display **:1**.
 
-#### 4. Remember the Exact Login Node, Where Your VNC Server Runs
+#### 4. Remember the Exact Login Node Where Your VNC Server Runs
 
 ```console
 $ uname -n
@@ -113,11 +113,11 @@ Mind that you should connect through the SSH tunneled port. In this example it i
 $ vncviewer localhost:5901
 ```
 
-If you use Windows version of TurboVNC Viewer, just run the Viewer and use address **localhost:5901**.
+If you use the Windows version of TurboVNC Viewer, just run the Viewer and use the address **localhost:5901**.
 
 #### 9. Proceed to the Chapter "Access the Visualization Node"
 
-Now you should have working TurboVNC session connected to your workstation.
+Now you should have a working TurboVNC session connected to your workstation.
 
 #### 10. After You End Your Visualization Session
 
@@ -129,8 +129,8 @@ $ vncserver -kill :1
 
 ### Access the Visualization Node
 
-**To access the node use a dedicated PBS Professional scheduler queue
-qviz**. The queue has following properties:
+**To access the node use the dedicated PBS Professional scheduler queue
+qviz**. The queue has the following properties:
 
 | queue                        | active project | project resources | nodes | min ncpus | priority | authorization | walltime         |
 | ---------------------------- | -------------- | ----------------- | ----- | --------- | -------- | ------------- | ---------------- |
@@ -139,13 +139,13 @@ qviz**. The queue has following properties:
 Currently when accessing the node, each user gets 4 cores of a CPU allocated, thus approximately 16 GB of RAM and 1/4 of the GPU capacity.
 
 !!! note
-    If more GPU power or RAM is required, it is recommended to allocate one whole node per user, so that all 16 cores, whole RAM and whole GPU is exclusive. This is currently also the maximum allowed allocation per one user. One hour of work is allocated by default, the user may ask for 2 hours maximum.
+    If more GPU power or RAM is required, it is recommended to allocate one whole node per user, so that all 16 cores, the whole RAM, and the whole GPU is exclusive. This is currently also the maximum allocation allowed per user. One hour of work is allocated by default, the user may ask for 2 hours maximum.
 
 To access the visualization node, follow these steps:
 
-#### 1. In Your VNC Session, Open a Terminal and Allocate a Node Using PBSPro qsub Command
+#### 1. In Your VNC Session, Open a Terminal and Allocate a Node Using the PBSPro qsub Command
 
-This step is necessary to allow you to proceed with next steps.
+This step is necessary to allow you to proceed with the next steps.
 
 ```console
 $ qsub -I -q qviz -A PROJECT_ID
@@ -159,9 +159,9 @@ $ qsub -I -q qviz -A PROJECT_ID -l select=1:ncpus=16 -l walltime=02:00:00
 
 Substitute **PROJECT_ID** with the assigned project identification string.
 
-In this example a whole node for 2 hours is requested.
+In this example a whole node is requested for 2 hours.
 
-If there are free resources for your request, you will have a shell unning on an assigned node. Please remember the name of the node.
+If there are free resources for your request, you will have a shell running on an assigned node. Please remember the name of the node.
 
 ```console
 $ uname -n
@@ -178,7 +178,7 @@ Setup the VirtualGL connection to the node, which PBSPro allocated for our job.
 $ vglconnect srv8
 ```
 
-You will be connected with created VirtualGL tunnel to the visualization ode, where you will have a shell.
+You will be connected with the created VirtualGL tunnel to the visualization node, where you will have a shell.
 
 #### 3. Load the VirtualGL Module
 
@@ -186,13 +186,13 @@ You will be connected with created VirtualGL tunnel to the visualization ode, wh
 $ module load virtualgl/2.4
 ```
 
-#### 4. Run Your Desired OpenGL Accelerated Application Using VirtualGL Script "Vglrun"
+#### 4. Run Your Desired OpenGL Accelerated Application Using the VirtualGL Script "Vglrun"
 
 ```console
 $ vglrun glxgears
 ```
 
-If you want to run an OpenGL application which is vailable through modules, you need at first load the respective module. E.g. to run the **Mentat** OpenGL application from **MARC** software ackage use:
+If you want to run an OpenGL application which is available through modules, you need to first load the respective module. E.g. to run the **Mentat** OpenGL application from **MARC** software package use:
 
 ```console
 $ module load marc/2013.1
@@ -201,7 +201,7 @@ $ vglrun mentat
 
 #### 5. After You End Your Work With the OpenGL Application
 
-Just logout from the visualization node and exit both opened terminals nd end your VNC server session as described above.
+Just logout from the visualization node and exit both opened terminals and end your VNC server session as described above.
 
 ## Tips and Tricks