# Labeling Fixes

docs/guides/8_6_installation.md

@@ -1,10 +1,10 @@
 ---
-Title: Installing Rocky Linux 8.6
+Title: Installing Rocky Linux 8
 author: wale soyinka
 contributors: tianci li, Steven Spencer
 ---
 
-# Installing Rocky Linux 8.6
+# Installing Rocky Linux 8
 
 This guide walks through the detailed steps to install a 64-bit version of the Rocky Linux distribution on a stand-alone system.  We will be performing a server class install using an operating system installer image downloaded from the Rocky Linux project website. We will step through the installation and customization steps in the following sections.
 

docs/guides/backup/rsnapshot_backup.md

@@ -1,5 +1,5 @@
 ---
-title: Backup Solution - _rsnapshot_
+title: Backup Solution - rsnapshot
 author: Steven Spencer
 contributors: Ezequiel Bruni
 tested with: 8.5, 8.6, 9.0

docs/guides/dns/private_dns_server_using_bind.md

@@ -233,9 +233,9 @@ Assuming that everything looks good, go ahead and restart _bind_:
 systemctl restart named
 ```
 
-=== "9.0"
+=== "9"
 
-    ## 9.0 Using IPv4 On Your LAN
+    ## 9 Using IPv4 On Your LAN
 
     In order to use ONLY IPv4 on your LAN, you need to make one change in `/etc/sysconfig/named`:
 
@@ -250,7 +250,7 @@ systemctl restart named
 
     Now save those changes (again, for _vi_, `SHIFT:wq!`)
 
-    ## 9.0 Testing Machines
+    ## 9 Testing Machines
 
     You need to add the DNS server (in our example 192.168.1.136) to each machine that you want to have access to the servers that you added to your local DNS. We are only going to show you an example of how to do this on a Rocky Linux workstation, but there are similar methods for other Linux distributions, as well as Windows and Mac machines.
 
@@ -327,7 +327,7 @@ systemctl restart named
 
     Once you've added the DNS servers that you want to the connection, you should be able to resolve hosts in *ourdomain.lan*, as well as Internet hosts.
 
-    ## 9.0 Firewall Rules - `firewalld`
+    ## 9 Firewall Rules - `firewalld`
 
     !!! note "`firewalld` By Default"
 
@@ -407,9 +407,9 @@ systemctl restart named
 
     These rules should get you DNS resolution on your private DNS server from hosts on the 192.168.1.0/24 network. In addition, you should be able to SSH from any of those hosts into your private DNS server.
 
-=== "8.6"
+=== "8"
 
-    ## 8.6 Using IPv4 On Your LAN
+    ## 8 Using IPv4 On Your LAN
 
     If you are using IPv4 only on your LAN, then you need to make two changes. The first is in `/etc/named.conf` and the second is in `/etc/sysconfig/named`
 
@@ -440,7 +440,7 @@ systemctl restart named
     Now save those changes (again, for _vi_, `SHIFT:wq!`)
 
 
-    ## 8.6 Testing Machines
+    ## 8 Testing Machines
 
     You need to add the DNS server (in our example 192.168.1.136) to each machine that you want to have access to the servers that you added to your new local DNS. We are only going to show you an example of how to do this on a Rocky Linux workstation, but there are similar methods for other Linux distributions, as well as Windows and Mac machines.
 
@@ -493,13 +493,13 @@ systemctl restart named
 
     Now you should be able to get to anything in the *ourdomain.lan* domain from your workstations, plus still be able to resovle and get to Internet addresses.
 
-    ## 8.6 Firewall Rules
+    ## 8 Firewall Rules
 
     ### Adding The Firewall Rules - `iptables`
 
     !!! note "Regarding `iptables`"
 
-        While `iptables` rules still work in Rocky Linux 8.6, we recommend moving to the `firewalld` rules in the section below. The reason is that in future versions of Rocky Linux, `iptables` will be deprecated and removed. In addition, `firewalld` is the default way of doing things. You will find more examples of using `firewalld` when looking for help, than for using `iptables`. We've included the `iptables` rules here, but for the best results and for future-proofing, we recommend moving to `firewalld` now.
+        While `iptables` rules still work in Rocky Linux 8.x, we recommend moving to the `firewalld` rules in the section below. The reason is that in future versions of Rocky Linux, `iptables` will be deprecated and removed. In addition, `firewalld` is the default way of doing things. You will find more examples of using `firewalld` when looking for help, than for using `iptables`. We've included the `iptables` rules here, but for the best results and for future-proofing, we recommend moving to `firewalld` now.
 
     First, create a file in */etc* called "firewall.conf" that will contain the following rules. This is a bare minimum rule set, and you may need to tweak this for your environment:
 

docs/guides/network/basic_network_configuration.md

@@ -19,11 +19,11 @@ You can't do much with a computer these days without network connectivity. Wheth
 * Elevated or administrative privileges on the system (For example root, `sudo` and so on)
 * Optional: familiarity with networking concepts
 
-=== "9.0"
+=== "9"
 
-    ## Network Configuration - Rocky Linux 9.0
+    ## Network Configuration - Rocky Linux 9
 
-    A lot has changed with network configuration as of Rocky Linux 9.0. One of the major changes is the move from Network-Scripts (still available to install-but effectively deprecated) to the use of Network Manager and key files, rather than `ifcfg` based files. `NetworkManager` as of 9.0, prioritizes `keyfiles` over the previous `ifcfg` files. Since this is now the default, the act of configuring the network should now take the default as the proper way of doing things, given that other changes over the years have meant the eventual deprecation and removal of older utilities. This guide will attempt to walk you through the use of Network Manager and the latest changes within Rocky Linux 9.0. 
+    A lot has changed with network configuration as of Rocky Linux 9. One of the major changes is the move from Network-Scripts (still available to install-but effectively deprecated) to the use of Network Manager and key files, rather than `ifcfg` based files. `NetworkManager` as of 9, prioritizes `keyfiles` over the previous `ifcfg` files. Since this is now the default, the act of configuring the network should now take the default as the proper way of doing things, given that other changes over the years have meant the eventual deprecation and removal of older utilities. This guide will attempt to walk you through the use of Network Manager and the latest changes within Rocky Linux 9. 
 
     ## Prerequisites
 
@@ -72,8 +72,8 @@ You can't do much with a computer these days without network connectivity. Wheth
 
     !!! Hint "Configuration Storage Location"
 
-        In Rocky Linux 8.6, the storage location for network configuration was in `/etc/sysconfig/Network-Scripts/`.
-        With Rocky Linux 9.0, the new default storage location for the key files is in `/etc/NetworkManager/system-connections`. 
+        In Rocky Linux 8, the storage location for network configuration was in `/etc/sysconfig/Network-Scripts/`.
+        With Rocky Linux 9, the new default storage location for the key files is in `/etc/NetworkManager/system-connections`. 
 
     The primary (but not the only) utility used for configuring a network interface is the `nmtui` command. This can also be done with the `nmcli` command, but is much less intuitive. We can show the interface as it is currently configured using `nmcli` with: 
 
@@ -237,7 +237,7 @@ You can't do much with a computer these days without network connectivity. Wheth
 
     !!! note 
 
-        While it is still possible to use this method for bringing the interface up and down in Rocky Linux 9.0, the command reacts a great deal slower than simply using the `nmcli` command in our previous examples.
+        While it is still possible to use this method for bringing the interface up and down in Rocky Linux 9, the command reacts a great deal slower than simply using the `nmcli` command in our previous examples.
 
     To bring the *enp0s3* down and up again we can simply use: 
 
@@ -353,11 +353,11 @@ You can't do much with a computer these days without network connectivity. Wheth
 
     ## Conclusions
 
-    There are a great deal of changes to the networking stack in Rocky Linux 9.0. Among these are the prioritization of `keyfile` over the formerly used `ifcfg` files found in Network-Scripts. Since it is evident that the direction of movement here in future versions of Rocky Linux will completely deprecate and remove Network-Scripts as an option, it's best to focus attention on methodologies such as `nmcli`, `nmtui`, and in some cases `ip`, for network configuration.
+    There are a great deal of changes to the networking stack in Rocky Linux 9. Among these are the prioritization of `keyfile` over the formerly used `ifcfg` files found in Network-Scripts. Since it is evident that the direction of movement here in future versions of Rocky Linux will completely deprecate and remove Network-Scripts as an option, it's best to focus attention on methodologies such as `nmcli`, `nmtui`, and in some cases `ip`, for network configuration.
 
-=== "8.6"
+=== "8"
 
-    ## Network Configuration - Rocky Linux 8.6
+    ## Network Configuration - Rocky Linux 8
 
     ## Using NetworkManager service
 
@@ -700,4 +700,4 @@ You can't do much with a computer these days without network connectivity. Wheth
 
     ## Conclusions
 
-    Rocky Linux 8.6 has the tools to configure your network from the command line. This document should get you up and running with those tools in no time.
+    Rocky Linux 8 has the tools to configure your network from the command line. This document should get you up and running with those tools in no time.