propose typo fixes

Author: jeis4wpi

.gitignore

@@ -2,6 +2,7 @@
 *.swo
 *.swp
 *.swn
+*~
 
 katello-installer*
 foreman-installer*

README.md

@@ -80,7 +80,7 @@ vagrant ssh centos9-stream-foreman-nightly
 
 To access the WebUI, it's helpful to have the vagrant-hostmanager plugin installed, so that your Workstation will automatically be able to resolve the hostname of the box to its IP address.
 
-Then you can simply open your browser and navigate to `https://centos9-stream-foreman-nightly.<HOSTNAME>.example.com` where `<HOSTNAME>` is replaced by the shortname of your workstation. The first time you do this you will need to accept the self-signed certicate.
+Then you can simply open your browser and navigate to `https://centos9-stream-foreman-nightly.<HOSTNAME>.example.com` where `<HOSTNAME>` is replaced by the shortname of your workstation. The first time you do this you will need to accept the self-signed certificate.
 
 By default, `forklift` deploys Foreman with `admin`/`changeme` as username and password.
 
@@ -166,7 +166,7 @@ allows completely automated dns resolution using dnsmasq from host to guest and
 
 You can disable hostmanager in `vagrant/settings.yaml` by setting `hostmanager_enabled` option.
 
-When using a briged network or with multiple network interfaces, the hostmanager would resolve the internal ip from the ssh-info, you can choose an ip of a particular network interface in `vagrant/settings.yaml` by setting `hostmanager_ip_resolver_device` option with the device name.
+When using a bridged network or with multiple network interfaces, the hostmanager would resolve the internal ip from the ssh-info, you can choose an ip of a particular network interface in `vagrant/settings.yaml` by setting `hostmanager_ip_resolver_device` option with the device name.
 
 ```yaml
 hostmanager_ip_resolver_device: 'eth1'
@@ -211,7 +211,7 @@ Options:
 | primary                  |  set the machine to be the default target of vagrant commands such as 'vagrant ssh' |
 | libvirt_qemu_use_session |  Use qemu session instead of system |
 
-Entirely new boxes can be created that do not orginate from a box defined within the Vagrantfile. For example, if you had access to a RHEL Vagrant box:
+Entirely new boxes can be created that do not originate from a box defined within the Vagrantfile. For example, if you had access to a RHEL Vagrant box:
 
 ```yaml
 rhel7:
@@ -275,7 +275,7 @@ with-sshfs:
 
 If you want to mount in the opposite direction, just change `reverse` to `False` or remove it entirely.
 
-Additonal options may be specified with using `options`.
+Additional options may be specified with using `options`.
 
 ```yaml
 with-sshfs-options:

docs/development.md

@@ -23,7 +23,7 @@ This covers how to setup and configure a development environment using the Forkl
 
 A Katello development environment can be deployed on Enterprise Linux (EL) distributions. Ensure that you have followed the steps to setup Vagrant and the libvirt plugin. There are a variety of useful development environment options that should or can be set when creating a development box. These options are designed to configure your environment ready to use your own fork, and create pull requests. To create a development box:
 
-1. Copy `vagrant/boxes.d/99-local.yaml.example` to `vagrant/boxes.d/99-local.yaml`.  
+1. Copy `vagrant/boxes.d/99-local.yaml.example` to `vagrant/boxes.d/99-local.yaml`.
 If you already have a `99-local.yaml`, you can copy the entries in `99-local.yaml.example` to your `99-local.yaml`.
 2. Fill in any ansible options, examples:
     * `foreman_devel_github_push_ssh`: Force git to push over SSH when HTTPS remote is configured
@@ -360,7 +360,7 @@ To use:
 
 ## Advanced features
 
-These are playbooks, roles and variables provided to use additional funcionalities to test advanced foreman features.
+These are playbooks, roles and variables provided to use additional functionalities to test advanced foreman features.
 This list should be organized by foreman feature.
 
 * [Kerberos](#foreman-with-active-directory)
@@ -371,7 +371,7 @@ This list should be organized by foreman feature.
 
 You need the AD controller with domain controller you want to test this against.
 Easiest is to install Windows server (ideally core to save resources, but its harder to install AD and setup DNS).
-This controller doesn't need to be searchable in your environmnet, we will point libvirt there.
+This controller doesn't need to be searchable in your environment, we will point libvirt there.
 
 I will be using the domain `example.com` and expect your AD controller runs on IP `192.0.2.8`.
 

docs/provision.md

@@ -7,7 +7,7 @@ host.
 
 ## How to configure
 
-1. If necessary, enable nested virt on your phyiscal box (see in [Checking if nested virtualization is supported](https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm)). Essentially, add this line to kvm-intel.conf and reboot:
+1. If necessary, enable nested virt on your physical box (see in [Checking if nested virtualization is supported](https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm)). Essentially, add this line to kvm-intel.conf and reboot:
 
     ```
     echo "options kvm-intel nested=1" | sudo tee /etc/modprobe.d/kvm-intel.conf
@@ -16,7 +16,7 @@ host.
 2. Build a box
     * Option 1: Use the `centos9-provision-nightly` box.
 
-    * Option 2: Use an existing Katello box (e.g. centos9-stream-katello-nightly) and run the provisioning playbook (it takes a while, as it syncs (on-demand) CentOS Stream 9, Puppet 7).  
+    * Option 2: Use an existing Katello box (e.g. centos9-stream-katello-nightly) and run the provisioning playbook (it takes a while, as it syncs (on-demand) CentOS Stream 9, Puppet 7).
     NOTE: If you are using Puppet 7 or higher, you need to increase the ram on the box, to something like 8096 otherwise candlepin crashes with OOM.
 
         ```
@@ -28,7 +28,7 @@ host.
     * Click "libvirt"
     * Click Compute profiles
     * Click 2-Medium
-        * increse ram to 2048MB (required for CentOS Stream 9)
+        * increase ram to 2048MB (required for CentOS Stream 9)
         * change network type to NAT, network name = provision
     * Click Submit
 4. Configure Activation Key

docs/troubleshooting.md

@@ -36,7 +36,7 @@ sudo service start nfs-server
 
 ## Low disk space
 
-Your OS may be installed with a large root parition and smaller `/home`
+Your OS may be installed with a large root partition and smaller `/home`
 partition. Vagrant will populate `~/.vagrant.d/` with boxes by default; each of
 which can be over 2GB in size. This may cause disk space issues on your `/home`
 partition.

packer/README.md

@@ -49,7 +49,7 @@ To create a version specific dev box, follow the directions above to install pac
 cd ./forklift/packer
 ```
 
-and run this comand (replacing 4.13 with the correct version):
+and run this command (replacing 4.13 with the correct version):
 
 ```sh
 ./scripts/build_stable_dev_box.rb 4.13