Merge pull request #6 from sebrandon1/typos

Fix some typos

Author: mwlinca

README.md

@@ -6,7 +6,7 @@ It is therefore recommended to wait for the workflow actions (https://github.com
 
 The latest release will be auto published (via Github-pages bot) to https://test-network-function.github.io/cnf-best-practices/
 
-The latest (and previous) PDF versions can be downloadeded from: https://github.com/test-network-function/cnf-best-practices/releases
+The latest (and previous) PDF versions can be downloaded from: https://github.com/test-network-function/cnf-best-practices/releases
 
 
 Contribution/PR Review Process: WIP

modules/cnf-best-practices-expectations-permissions.adoc

@@ -218,7 +218,7 @@ See test case link:https://github.com/test-network-function/cnf-certification-te
 
 OpenShift has a default scheduler that is responsible for the currently available resources on the platform, placing containers or applications on the platform appropriately. In order for OpenShift to do this correctly, the application developer must create a resource profile for the application. This resource profile contains requirements such as how much memory, CPU, and storage that the application needs. At this point, the scheduler is aware of what nodes in the cluster can satisfy the workload. It places the application on one of those nodes. The scheduler can also place the application pod in a pending state until resources are available.
 
-All pods should have a resource request that is the minimum amount o fresources the pod is expected to use at steady state for both memory and CPU.
+All pods should have a resource request that is the minimum amount of resources the pod is expected to use at steady state for both memory and CPU.
 
 [id="cnf-best-practices-storage:-emptydir"]
 ==== Storage: emptyDir
@@ -753,7 +753,7 @@ Openshift will wait until worker-10 is ready before proceeding onwards to worker
 
 In clusters larger than the example cluster, the `maxUnavailable` for the worker pool may be set to a large number to reboot multiple nodes in parallel to speed up deployment of the new version of OpenShift. This number will take into account the work loads on the cluster to make sure sufficient resources are left to maintain application availability.
 
-For an application to stay healthy during this process, if they are stateful at all, they should specify a statefulset or replicatset, kubernetes by default will attempt to schedule the set members across multiple nodes to give additional resiliency. In order to prevent kubernetes from stealing too many nodes out from under an application, an application that has a minimum number of pods that need to be running must specify a pod disruption budget. Pod disruption budgets allow an application to tell kubernetes that it needs N number of pods of said microservice alive at any given time. For example, a small stateful database may need 2 out of three pods available at any given time, so that application should set a pod disruption budget with a minavailable set to a value of 2. This will allow the scheduler to know that it should not take the second pod out of a set of 3 down at any given time during the series of node reboots.
+For an application to stay healthy during this process, if they are stateful at all, they should specify a statefulset or replicaset, kubernetes by default will attempt to schedule the set members across multiple nodes to give additional resiliency. In order to prevent kubernetes from stealing too many nodes out from under an application, an application that has a minimum number of pods that need to be running must specify a pod disruption budget. Pod disruption budgets allow an application to tell kubernetes that it needs N number of pods of said microservice alive at any given time. For example, a small stateful database may need 2 out of three pods available at any given time, so that application should set a pod disruption budget with a minavailable set to a value of 2. This will allow the scheduler to know that it should not take the second pod out of a set of 3 down at any given time during the series of node reboots.
 
 [NOTE]
 ====

modules/cnf-best-practices-linux-capabilities.adoc

@@ -4,7 +4,7 @@
 Linux Capabilities allow you to break apart the power of root into smaller groups of privileges. The link:https://man7.org/linux/man-pages/man7/capabilities.7.html[Linux capabilities(7)] man page provides a detailed description of how capabilities management is performed in Linux.
 In brief, the Linux kernel associates various capability sets with threads and files. The thread’s Effective capability set determines the current privileges of a thread.
 
-When a thread executes a binary program the kernel updates the various thread capability sets according to a set of rules that take into account the UID of thread before and after the exec system call and the file capabilities of the program being executed. Refer to the blog series in link:[10]# for more details about []Linux capabilities and some examples. For Red Hat specific review of capabilities please refer to thelink:Linux Capabilities in OpenShift blog.# An additional reference is link:Docker Run Reference.[]
+When a thread executes a binary program the kernel updates the various thread capability sets according to a set of rules that take into account the UID of thread before and after the exec system call and the file capabilities of the program being executed. Refer to the blog series in link:[10]# for more details about []Linux capabilities and some examples. For Red Hat specific review of capabilities please refer to the link:Linux Capabilities in OpenShift blog.# An additional reference is link:Docker Run Reference.[]
 
 Users may choose to specify the required permissions for their running application in the Security Context of the pod specification. In OCP, administrators can use the Security Context Constraint (SCC) admission controller plugin to control the permissions allowed for pods deployed to the cluster. If the pod requests permissions that are not allowed by the SCCs available to that pod, the pod will not be admitted to the cluster.