Review: rename file and fix command lines

doc.zih.tu-dresden.de/docs/archive/ram_disk_documentation.md → doc.zih.tu-dresden.de/docs/archive/ram_disk.md

-# Ramdisk
+# RAM Disk
 
-## Using parts of the main memory as a temporary file system
+!!! warning
 
-On systems with a very large main memory, it is for some workloads very
-attractive to use parts of the main memory as a temporary file system.
-This will reduce file access times dramatically and has proven to speed
-up applications that are otherwise limited by I/O.
+    This page is outdated.
 
-We provide tools to allow users to create and destroy their own
-ramdisks. Currently, this is only allowed on the SGI UV2 (venus). Please
-note that the content of the ramdisk will vanish immediatelly when the
-ramdisk is destroyed or the machine crashes. Always copy out result data
-written to the ramdisk to another location.
+On systems with a very large main memory, it is for some workloads very attractive to use parts of
+the main memory as a temporary file system.  This will reduce file access times dramatically and has
+proven to speed up applications that are otherwise limited by I/O.
 
-### Creating a ramdisk
+We provide tools to allow users to create and destroy their own ramdisks. Currently, this is only
+allowed on the SGI UV2 (venus). Please note that the content of the ramdisk will vanish immediatelly
+when the ramdisk is destroyed or the machine crashes. Always copy out result data written to the
+ramdisk to another location.
 
-On venus, the creation of ramdisks is only allowed from within an LSF
-job. The memory used for the ramdisk will be deducted from the memory
-assigned to the LSF job. Thus, the amount of memory available for an LSF
-job determines the maximum size of the ramdisk. Per LSF job only a
-single ramdisk can be created (but you can create and delete a ramdisk
-multiple times during a job). You need to load the corresponding
-software module via
+### Creating a RAM Disk
+
+On [Venus](hardware_venus.md), the creation of RAM disk is only allowed from within an LSF job. The
+memory used for the RAM disk will be deducted from the memory assigned to the LSF job. Thus, the
+amount of memory available for an LSF job determines the maximum size of the ramdisk. Per LSF job
+only a single ramdisk can be created (but you can create and delete a ramdisk multiple times during
+a job). You need to load the corresponding software module via
 
 ```Bash
 module load ramdisk
 ```
 
-Afterwards, the ramdisk can be created with the command
+Afterwards, the RAM disk can be created with the command
 
 ```Bash
-make-ramdisk «size of the ramdisk in GB»
+make-ramdisk «size of the ramdisk in GB»
 ```
 
 The path to the ramdisk is fixed to `/ramdisks/«JOBID»`.
@@ -43,7 +41,7 @@ can also be used to transfer single files but will only use one thread
 in this case. It is used as follows
 
 ```Bash
-parallel-copy.sh «source directory or file» «target directory»
+parallel-copy.sh «source directory or file» «target directory»
 ```
 
 It is not specifically tailored to be used with the ramdisk. It can be
@@ -65,5 +63,5 @@ ramdisk as its current path. Locating these processes, that block the
 destruction of the ramdisk is possible via using the command
 
 ```Bash
-lsof +d /ramdisks/«JOBID»
+lsof +d /ramdisks/«JOBID»
 ```

doc.zih.tu-dresden.de/mkdocs.yml

@@ -128,7 +128,7 @@ nav:
     - No IB Jobs: archive/no_ib_jobs.md
     - Phase2 Migration: archive/phase2_migration.md
     - Platform LSF: archive/platform_lsf.md
-    - RamDisk Documentation: archive/ram_disk_documentation.md
+    - RAM Disk: archive/ram_disk.md
     - System Altix: archive/system_altix.md
     - System Atlas: archive/system_atlas.md
     - System Venus: archive/system_venus.md