Linkcheck cleanup (#490)

Fixes #490.
Link cleanup/replacement where applicable, based on link checkup

contribute/contribute_documentation.rst

@@ -7,7 +7,7 @@ Steps for contributing to **rockstor-doc** repo are similar to contributing to
 **rockstor-core**, as we follow the same fork and pull request model. We'll
 assume you have basic proficiency with Git and are familiar with using a
 text editor or IDE of your choice. Emacs, Vim, Eclipse and PyCharm are some
-recommendations. Or you may be able to use an online such as https://livesphinx.herokuapp.com/.
+recommendations. Or you may be able to use an online editor such as https://www.tutorialspoint.com/online_restructure_editor.php.
 
 Environment setup
 -----------------
@@ -326,6 +326,5 @@ To expedite the review, please follow these two tips:
 * When you make a pull request, adding a "Fixes #number-of-issue" on its own
   line will automatically close the related issue when it gets merged. Just a
   nice thing to have and also provides a link to the relevant issue. See
-  `GitHub documentation <https://docs.github
-  .com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue>`_
+  `GitHub documentation <https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue>`_
   for details.

data_loss.rst

@@ -184,8 +184,8 @@ See our :ref:`support` options.
 If you are already knowledgeable in btrfs and system administration,
 see the upstream community `Libera Chat - #btrfs channel <https://web.libera.chat/#btrfs>`_.
 Finally, if your needs are extreme, consider seeking help on the
-`btrfs mailing list <http://vger.kernel.org/vger-lists.html#linux-btrfs>`_.
-More details on subscribing to the mailing list are available `here <http://vger.kernel.org/majordomo-info.html#taboo>`_.
+`btrfs mailing list (linux-btrfs) <https://subspace.kernel.org/vger.kernel.org.html>`_.
+More details on subscribing to the mailing list are available `here <https://subspace.kernel.org/subscribing.html>`_.
 
 .. warning::
 
@@ -205,8 +205,8 @@ Also take note of what you are usually expected to include:
 .. note::
 
    The :code:`dmesg` information output may be very large. If it is, instead of pasting it into the mail body,
-   it should be attached to the mail. However, check the restrictions on overall mail size
-   `here <http://vger.kernel.org/majordomo-info.html#taboo>`_.
+   it should be attached to the mail. However, check the restrictions on overall mail size on the
+   `etiquette page <https://subspace.kernel.org/etiquette.html>`_.
 
 .. _datalossraid0_single:
 

interface/overview.rst

@@ -318,7 +318,7 @@ settings summarized in the previous table.
 Add Labels
 ^^^^^^^^^^
 The **Add Labels** feature allows to apply customized *docker container labels*
-(`docker documentation <https://docs.docker.com/config/labels-custom-metadata/>`_)
+(`docker documentation <https://docs.docker.com/engine/manage-resources/labels/>`_)
 to any installed Rock-on. To add a new label within an existing Rock-on, make
 sure the Rock-on is turned OFF, and click on the little wrench icon next to the
 ON/OFF toggle to display a summary of the Rock-on's addlabels_settings_summary

interface/system/network.rst

@@ -58,7 +58,7 @@ other, granting external access to some, while preventing it from others. As a
 result, docker networks (rocknets) are ideal ways to connect a front-end
 container to a back-end database container, or connect multiple rock-ons
 together hidden behind a reverse-proxy rock-on. Please see
-`Docker's documentation <https://docs.docker.com/network/drivers/bridge>`_
+`Docker's documentation <https://docs.docker.com/engine/network/drivers/bridge/>`_
 for further details on the different features and settings of such networks.
 
 .. note::

interface/system/services.rst

@@ -68,7 +68,7 @@ Rockstor 4 relies on `SSSD <https://sssd.io/>`_ for the management of identities
 As a result, one can edit :code:`/etc/sssd/sssd.conf` to further customize the enrollment into an AD.
 
 Upon submission of the AD configuration form, Rockstor will test the configuration settings by attempting to *discover* the AD domain and save the configuration if successful.
-If Rockstor cannot discover the AD domain, it will report the error back to the Web-UI; notably, verify that the AD domain can be resolved by name via DNS (see `Red Hat Windows Integration Guide <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/windows_integration_guide/sssd-integration-intro#sssd-ad-proc>`_ for further documentation).
+If Rockstor cannot discover the AD domain, it will report the error back to the Web-UI; notably, verify that the AD domain can be resolved by name via DNS (see `Red Hat Windows Integration Guide <https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/windows_integration_guide/sssd-integration-intro>`_ for further documentation).
 
 Note that a successful configuration of the AD service does not enroll the system into the AD. To do this, the AD service must be turned ON. To leave the AD, simply turn the AD service OFF.