diff --git a/source/Installation/Testing.rst b/source/Installation/Testing.rst
index e33ca85527..c608d23c38 100644
--- a/source/Installation/Testing.rst
+++ b/source/Installation/Testing.rst
@@ -10,27 +10,27 @@ Usually, you will get the released version of binaries when following :doc:`../I
 There are also pre-released versions of binaries that are useful for testing before making an official release.
 This article describes several options if you would like to try out pre-released versions of ROS binaries.
 
-deb testing repository
-----------------------
-
 When packages are released into a ROS distribution (using bloom), the buildfarm builds them into deb packages which are stored temporarily in the **building** apt repository.
 As dependent packages are rebuilt, an automatic process periodically synchronizes the packages in **building** to a secondary repository called **ros-testing**.
 **ros-testing** is intended as a soaking area where developers and bleeding-edge users may give the packages extra testing, before they are manually synced into the public ros repository from which users typically install packages.
 
 Approximately every two weeks, the rosdistro's release manager manually synchronizes the contents of **ros-testing** into the **main** ROS repository.
 
+deb testing repository
+----------------------
+
 For Debian-based operating systems, you can install binary packages from the **ros-testing** repository.
 
 1. Make sure you have a working ROS 2 installation from deb packages (see :doc:`../Installation`).
 
-2. Install the ``ros2-testing-apt-source`` package
-   This will automatically uninstall the ``ros2-apt-source`` package since only one repository may be enabled at a time.
+2. Install the ros2-testing-apt-source package.
+   This will automatically uninstall the ros2-apt-source package since only one repository may be enabled at a time.
 
    .. code-block:: console
 
       $ sudo apt install -y ros2-testing-apt-source
 
-3. Update the ``apt`` index:
+3. Update the apt index:
 
    .. code-block:: console
 
@@ -48,11 +48,11 @@ For Debian-based operating systems, you can install binary packages from the **r
 
       $ sudo apt dist-upgrade
 
-6. Once you are finished testing, you can switch back to the normal repository by re-installing the ``ros-apt-source`` package:
+6. Once you are finished testing, you can switch back to the normal repository by re-installing the ros-apt-source package:
 
    .. code-block:: console
 
-      $ sudo apt install -y ros-apt-source
+      $ sudo apt install -y ros2-apt-source
 
    and doing an update and upgrade:
 
@@ -61,6 +61,47 @@ For Debian-based operating systems, you can install binary packages from the **r
       $ sudo apt update
       $ sudo apt dist-upgrade
 
+
+RHEL testing repository
+-----------------------
+
+For RHEL you can install binary packages from the **ros-testing** repository, by enabling the testing repository on the source configuration:
+
+1. Make sure you have a working ROS 2 installation for rpm packages (see the :doc:`RHEL installation instructions <RHEL-Install-RPMs>`).
+
+2. Enable testing and disable main repository:
+
+   .. code-block:: console
+
+      $ sudo dnf config-manager setopt ros2-testing.enabled=1
+      $ sudo dnf config-manager setopt ros2.enabled=0
+
+3. Update the dnf index:
+
+   .. code-block:: console
+
+      $ sudo dnf update
+
+4.  You can now install individual packages from the testing repository, for example:
+
+   .. code-block:: console
+
+      $ sudo dnf install ros-{DISTRO}-my-just-released-package
+
+5.  Once you are finished testing, you can switch back to the normal repository by re-enabling the main repository:
+
+   .. code-block:: console
+
+      $ sudo dnf config-manager setopt ros2-testing.enabled=0
+      $ sudo dnf config-manager setopt ros2.enabled=1
+
+   and doing an update and upgrade:
+
+   .. code-block:: console
+
+      $ sudo dnf update
+      $ sudo dnf system-upgrade
+
 .. _Prerelease_binaries:
 
 Binary archives