diff --git a/docs/guides/virtualization/cockpit-machines.md b/docs/guides/virtualization/cockpit-machines.md
index 6971a4384c..54b44361e6 100644
--- a/docs/guides/virtualization/cockpit-machines.md
+++ b/docs/guides/virtualization/cockpit-machines.md
@@ -11,7 +11,7 @@ tags:
 
 ## Introduction
 
-Cockpit is a server administration tool which provides an easy-to-use dashboard to manage your server. One feature of Cockpit is that with a package, it can manage KVM virtual machines from a web interface similar to VMware ESXi or Proxmox.
+Cockpit is a server administration tool that provides an easy-to-use dashboard to manage your server. One feature of Cockpit is that with a package, it can manage KVM virtual machines from a web interface similar to VMware ESXi or Proxmox.
 
 ## Prerequisites
 
@@ -20,7 +20,7 @@ Cockpit is a server administration tool which provides an easy-to-use dashboard
 
 ## Installing Cockpit
 
-Cockpit comes by default in Rocky Linux, however, KVM support doesn't come installed out-of-the-box. We'll install it via `dnf`:
+Cockpit comes by default in Rocky Linux. However, KVM support does not come installed out-of-the-box. We will install it via `dnf`:
 
 ```bash
 dnf install -y cockpit-machine
@@ -34,23 +34,23 @@ dnf install -y libvirtd
 
 ## Enabling `cockpit`
 
-To actually enable both KVM virtualization and Cockpit, enable the systemd services:
+To enable both KVM virtualization and Cockpit, enable the `systemd` services:
 
 ```bash
 systemctl enable --now libvirtd cockpit
 ```
 
-After you enabled `cockpit`, open a browser to http://ip_address:9090 (note: replace "ip_address" with the IP address of your server):
+After you enable `cockpit`, open a browser to http://ip_address:9090 (note: replace "ip_address" with the IP address of your server):
 
 ![Cockpit login screen](../images/cockpit_login.png)
 
-Login as a non-root user and you should see a dashboard similar to the one shown here:
+Login as a non-root user, and you should see a dashboard similar to the one shown here:
 
 ![Cockpit dashboard](../images/cockpit_dashboard.png)
 
 ## Creating a virtual machine
 
-In this guide, you will create a Rocky Linux 9 virtual machine on your host system where you use automation to add a username and root password.
+In this guide, you will create a Rocky Linux 9 virtual machine on your host system, using automation to add a username and root password.
 
 To create a virtual machine in Cockpit, first click on the blue **Turn on administrative access** button, and enter your password if needed:
 
@@ -78,7 +78,7 @@ In a few minutes, select your newly-created VM, you will have its IP address:
 
 ![Our VM's IP address](../images/cockpit_vm_ip.png)
 
-SSH into your hypervisor, and subsequently SSH into the IP address from Cockpit. In this example, it is **172.20.0.103**. You will be logged into your new server:
+SSH into your hypervisor, and SSH into the IP address from Cockpit. In this example, it is **172.20.0.103**. You will be logged into your new server:
 
 ![Our VM's terminal](../images/cockpit_vm_terminal.png)
 
@@ -89,8 +89,8 @@ While Cockpit is great for creating and managing virtual machines, there are a f
 * You cannot create a bridge interface.
 * You cannot create a new image in any storage pool, only the `default` one.
 
-Fortunately, these can be created using the command line, and subsequently used by way of Cockpit.
+Fortunately, you can create these at the command line, and then Cockpit can use them.
 
 ## Conclusion
 
-Cockpit is an invaluable tool for managing a Rocky Linux server via a web interface. It is personally the author's go-to tool for creating virtual machines in their home lab. While `cockpit-machines` may not be as full-featured as ESXi or Proxmox, for 90% of hypervisor use cases, it gets the job done.
+Cockpit is an invaluable tool for managing a Rocky Linux server via a web interface. It is personally the author's go-to tool for creating virtual machines in their home lab. While `cockpit-machines` may not be as full-featured as ESXi or Proxmox, it gets the job done for 90% of hypervisor use cases.
diff --git a/docs/guides/web/tor_onion_service.md b/docs/guides/web/tor_onion_service.md
index 8c0054212e..8f87602b16 100644
--- a/docs/guides/web/tor_onion_service.md
+++ b/docs/guides/web/tor_onion_service.md
@@ -65,7 +65,7 @@ HiddenServicePort 80 127.0.0.1:80
 
 ## Configuring a web server
 
-You will also need a web server on our machine to service clients to your onion service. Any web server is usable (Caddy, Apache, or Nginx). The author prefers Caddy. For simplicity's sake, install Caddy:
+You will also need a web server on our machine to service clients to your onion service. Any web server (Caddy, Apache, or Nginx) is usable. The author prefers Caddy. For simplicity's sake, install Caddy:
 
 ```bash
 dnf -y install caddy