Fix misspellings (coreos#154)

README.md

@@ -33,7 +33,7 @@ This repository contains the Fedora CoreOS documentation. The format is [AsciiDo
 
 Antora introduces two new terms:
 
-* **Component** — Simply put, a component is a part of the documentation website with its own menu. Components can also be versioned. In the Fedora Docs, we use separate components for user documentation, the Fedora Poject, Fedora council, Mindshare, FESCO, but also subprojects such as CommOps or Modulartity.
+* **Component** — Simply put, a component is a part of the documentation website with its own menu. Components can also be versioned. In the Fedora Docs, we use separate components for user documentation, the Fedora Project, Fedora council, Mindshare, FESCO, but also subprojects such as CommOps or Modulartity.
 * **Module** — A component can be broken down into multiple modules. Modules still share a single menu on the site, but their sources can be stored in different git repositories, even owned by different groups. The default module is called "ROOT" (that's what is in this example). If you don't want to use multiple modules, only use "ROOT". But to define more modules, simply duplicate the "ROOT" directory and name it anything you want. You can store modules in one or more git repositories.
 
 ## Local preview

antora.yml

@@ -1,4 +1,4 @@
-# Name will be mostly visible in the URL. Treat it as an indentifier.
+# Name will be mostly visible in the URL. Treat it as an identifier.
 # Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page)
 name: fedora-coreos  # <---- PLEASE MODIFY
 

build.sh

@@ -14,7 +14,7 @@ if [ "$(uname)" == "Darwin" ]; then
 
 elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then
     # Running on Linux.
-    # Check whether podman is available, else faill back to docker
+    # Check whether podman is available, else fall back to docker
     # which requires root.
 
     if [ -f /usr/bin/podman ]; then

modules/ROOT/pages/access-recovery.adoc

@@ -1,6 +1,6 @@
 = Access Recovery
 
-If you've lost the private key of an SSH keypair used to log into Fedora CoreOS, and do not have any password logins set up to use at the console, you can gain access back to the machine by booting into single user mode with the `single` kernel command-line argument:
+If you've lost the private key of an SSH key pair used to log into Fedora CoreOS, and do not have any password logins set up to use at the console, you can gain access back to the machine by booting into single user mode with the `single` kernel command-line argument:
 
 . When booting the system, intercept the GRUB menu and edit the entry to append `single` to the kernel argument list, then press Ctrl-X to resume booting.
 . Wait for the system to boot into a shell prompt

modules/ROOT/pages/fcos-projects.adoc

@@ -3,6 +3,6 @@
 This a list of projects that are actively using Fedora CoreOS:
 
 * https://www.okd.io[OKD] is the Community Distribution of Kubernetes that powers https://www.openshift.com/products/container-platform[Red Hat OpenShift Container Platform]. By default, Fedora CoreOS is the underlying OS used by the control plane nodes and the worker nodes.
-* https://github.com/poseidon/typhoon[Typhoon] is a minimal and free Kubernetes distribution. Users of Typhoon have the option of using Fedora CoreOS as the undelying OS for their nodes.
+* https://github.com/poseidon/typhoon[Typhoon] is a minimal and free Kubernetes distribution. Users of Typhoon have the option of using Fedora CoreOS as the underlying OS for their nodes.
 * https://wiki.openstack.org/wiki/Magnum[OpenStack Magnum] is an OpenStack API service developed by the OpenStack Containers Team making container orchestration engines such as Docker Swarm, Kubernetes, and Apache Mesos available as first class resources in OpenStack. Fedora CoreOS is used as the underlying OS for nodes that are provisioned via Magnum.
 * https://www.ovirt.org/develop/release-management/features/virt/coreos-ignition-support.html[oVirt] supports booting Fedora CoreOS nodes and has native support for https://github.com/coreos/ignition[Ignition] configurations.

modules/ROOT/pages/live-booting-ipxe.adoc

@@ -39,4 +39,4 @@ boot
 
 Since the traditional FCOS upgrade process requires a disk, live-PXE systems are not able to auto-update in place. For this reason, Zincati is not running there.
 
-Instead, it is reccomended that images references in the PXE configuration are regularly refreshed. Once infrastructure and configurations are updated, the live-PXE instance simply needs to be rebooted in order to start running the new FCOS version.
+Instead, it is recommended that images references in the PXE configuration are regularly refreshed. Once infrastructure and configurations are updated, the live-PXE instance simply needs to be rebooted in order to start running the new FCOS version.

modules/ROOT/pages/tutorial-updates.adoc

@@ -95,7 +95,7 @@ Run `fcct` to convert that to an Ignition config:
 fcct --pretty --strict fcct-updates.yaml --output updates.ign
 ----
 
-== Startup and intial update
+== Startup and initial update
 
 Now let's provision it. Make sure that you are starting from the older Fedora CoreOS image in this step: