Rename to general and anselm

docs.it4i/anselm-cluster-documentation/storage.md → docs.it4i/anselm/storage.md

@@ -107,7 +107,7 @@ The HOME filesystem is mounted in directory /home. Users home directories /home/
 
 The HOME filesystem should not be used to archive data of past Projects or other unrelated data.
 
-The files on HOME filesystem will not be deleted until end of the [users lifecycle](../get-started-with-it4innovations/obtaining-login-credentials/obtaining-login-credentials/).
+The files on HOME filesystem will not be deleted until end of the [users lifecycle](../general/obtaining-login-credentials/obtaining-login-credentials/).
 
 The filesystem is backed up, such that it can be restored in case of catasthropic failure resulting in significant data loss. This backup however is not intended to restore old versions of user data or to restore (accidentaly) deleted files.
 

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/vnc.md → docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md

@@ -198,7 +198,7 @@ Allow incoming X11 graphics from the compute nodes at the login node:
 $ xhost +
 ```
 
-Get an interactive session on a compute node (for more detailed info [look here](../../../anselm-cluster-documentation/resource-allocation-and-job-execution/job-submission-and-execution/)). Use the **-v DISPLAY** option to propagate the DISPLAY on the compute node. In this example, we want a complete node (24 cores in this example) from the production queue:
+Get an interactive session on a compute node (for more detailed info [look here](../../../anselm/resource-allocation-and-job-execution/job-submission-and-execution/)). Use the **-v DISPLAY** option to propagate the DISPLAY on the compute node. In this example, we want a complete node (24 cores in this example) from the production queue:
 
 ```bash
 $ qsub -I -v DISPLAY=$(uname -n):$(echo $DISPLAY | cut -d ':' -f 2) -A PROJECT_ID -q qprod -l select=1:ncpus=24

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/introduction.md → docs.it4i/general/accessing-the-clusters/introduction.md

@@ -3,7 +3,7 @@
 The IT4Innovations clusters are accessed by SSH protocol via login nodes.
 
 !!! note
-    Read more on [Accessing the Salomon Cluster](../../salomon/shell-and-data-access.md) or [Accessing the Anselm Cluster](../../anselm-cluster-documentation/shell-and-data-access.md) pages.
+    Read more on [Accessing the Salomon Cluster](../../salomon/shell-and-data-access.md) or [Accessing the Anselm Cluster](../../anselm/shell-and-data-access.md) pages.
 
 ## PuTTY
 

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/vpn1-access.md → docs.it4i/general/accessing-the-clusters/vpn1-access.md

@@ -5,7 +5,7 @@
 !!! note
     **Failed to initialize connection subsystem Win 8.1 - 02-10-15 MS patch**
 
-Workaround can be found at [vpn-connection-fail-in-win-8.1](../../get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/vpn-connection-fail-in-win-8.1.html)
+Workaround can be found at [vpn-connection-fail-in-win-8.1](../../general/accessing-the-clusters/shell-access-and-data-transfer/vpn-connection-fail-in-win-8.1.html)
 
 For using resources and licenses which are located at IT4Innovations local network, it is necessary to VPN connect to this network. We use Cisco AnyConnect Secure Mobility Client, which is supported on the following operating systems: