Fix various issues.

Signed-off-by: Volker Theile <volker.theile@openmediavault.org>

administration/access_rights_management.rst

@@ -99,7 +99,7 @@ fields.
 Edit
 ^^^^
 Just to add or remove members from groups. Default groups created in the
-|webui| have a gid greater than 1000. Same as usernames that are created
+|webui| have a gid greater than ``1000``. Same as usernames that are created
 in CLI they are not stored in the internal database. Just edit, insert a
 comment.
 
@@ -170,12 +170,12 @@ When a plugin or a service uses a |sf| its stores the uuid only. Later on
 using helper scripts or internal CLI |omv| commands the path can be obtained
 just by using the :code:`uuid` number.
 A shared folder can be used across all over the system backend. Is available
-to select it in sharing services (FTP, Samba, RSync, etc) at the same time.
+to select it in sharing services (FTP, Samba, RSync, etc.) at the same time.
 Plugins can use them also just by using the shared folder combo class.
 
 .. note::
 	- A |sf| belongs to an |omv| filesystem entry. Is not possible to unmount the filesystem volume without deleting the folder configuraton from the |webui|.
-	- If a |sf| is being used by a service (FTP, plugins, etc) is not possible to delete it. Is necessary to disengage the |sf| from the service(s) or section(s) that is holding it before proceeding with removal of the configuration. This will also prevent to unmount a device from the |webui| in the filesystem section if there is still a |sf| associated with it.
+	- If a |sf| is being used by a service (FTP, plugins, etc.) is not possible to delete it. Is necessary to disengage the |sf| from the service(s) or section(s) that is holding it before proceeding with removal of the configuration. This will also prevent to unmount a device from the |webui| in the filesystem section if there is still a |sf| associated with it.
 	- Due to the design of the software is not possible at the moment to know what section or service is holding which |sf|.
 
 Edit

faq.rst

@@ -47,7 +47,7 @@ How can I modify or add a network configuration of :file:`/etc/network/interface
 	The interfaces file is controlled by |omv|. To add network interfaces that are not configurable through the |webui| or other options not present, you need to use  :doc:`advanced settings <various/advset>`.
 
 Why my disks mount paths have a long alphanumeric number?
-	The long number is called UUID, it is used by fstab to mount disks. This number is unique per filesystem (or at least unlikely possible that another filesystem comes with an identical one). This helps maintaing the mount points. The old linux way (sda1, sdb1, etc) is not guaranteed that /sda1 is the same disk on next reboot. If you have trouble identiying them in terminal, you can always create a pool with symlinks to each file system with easy to remember names.
+	The long number is called UUID, it is used by fstab to mount disks. This number is unique per filesystem (or at least unlikely possible that another filesystem comes with an identical one). This helps maintaing the mount points. The old linux way (sda1, sdb1, etc.) is not guaranteed that /sda1 is the same disk on next reboot. If you have trouble identiying them in terminal, you can always create a pool with symlinks to each file system with easy to remember names.
 
 	This behaviour has been deprecated now in current omv releases including stable (Jessie). The default creation of mount paths is documented `here <https://github.com/openmediavault/openmediavault/blob/20ec529737e6eca2e1f98d0b3d1ade16a3c338e1/deb/openmediavault/usr/share/openmediavault/engined/rpc/filesystemmgmt.inc#L823-L833>`_.
 

various/filesystems.rst

@@ -11,7 +11,7 @@ Overview
 	- Predictable device path of the filesystem  <fsname>
 	- Target mount directory <dir>
 	- Filesystem options <opts>
-	- Filesystem type (ext3, ext4, etc) <type>
+	- Filesystem type (EXT3, EXT4, etc.) <type>
 
 	You can inspect a mntent entry in config.xml it should look like this: