Fixed typos

knowledge base/keda.md

@@ -6,21 +6,21 @@ Any Kubernetes cluster **>= 1.16.0** should work.
 
 **Table of contents:**
 
-- [How KEDA works](#how-keda-works)
-- [Deployment](#deployment)
-  - [Helm chart](#helm-chart)
-  - [Manual deployment](#manual-deployment)
-- [Usage](#usage)
-  - [ScaledObject](#scaledobject)
-  - [ScaledJobs](#scaledjobs)
-  - [Authentication](#authentication)
-- [External Scalers](#external-scalers)
-- [Troubleshooting](#troubleshooting)
-  - [Access logging and telemetry](#access-logging-and-telemetry)
-  - [Long running executions](#long-running-executions)
-  - [Manually uninstall everything](#manually-uninstall-everything)
-- [Further readings](#further-readings)
-- [Sources](#sources)
+1. [How KEDA works](#how-keda-works)
+2. [Deployment](#deployment)
+   1. [Helm chart](#helm-chart)
+   2. [Manual deployment](#manual-deployment)
+3. [Usage](#usage)
+   1. [ScaledObject](#scaledobject)
+   2. [ScaledJobs](#scaledjobs)
+   3. [Authentication](#authentication)
+4. [External Scalers](#external-scalers)
+5. [Troubleshooting](#troubleshooting)
+   1. [Access logging and telemetry](#access-logging-and-telemetry)
+   2. [Long running executions](#long-running-executions)
+   3. [Manually uninstall everything](#manually-uninstall-everything)
+6. [Further readings](#further-readings)
+7. [Sources](#sources)
 
 ## How KEDA works
 
@@ -86,7 +86,7 @@ VERSION=2.0.0 make undeploy  # uninstallation
 
 ## Usage
 
-One can just add a resouce to their deployment using the Custom Resource Definitions KEDA offers:
+One can just add a resource to their deployment using the Custom Resource Definitions KEDA offers:
 
 - **ScaledObject** for Deployments, StatefulSets and Custom Resources
 - **ScaledJob** for Jobs
@@ -174,7 +174,7 @@ For details and updated information see KEDA's [Scaling Jobs] page.
 
 The ScaledJob Custom Resource definition is what defines how KEDA should scale a Job and what the triggers (_scalers_) are. The full list of scalers is available [here][scalers].
 
-Instead of scaling up the number of replicas, KEDA will schedule a single Job for each detected event. For this, a ScaledJob is primarly used for long running executions or small tasks being able to run in parallel in massive spikes like processing queue messages:
+Instead of scaling up the number of replicas, KEDA will schedule a single Job for each detected event. For this, a ScaledJob is primarily used for long running executions or small tasks being able to run in parallel in massive spikes like processing queue messages:
 
 ```yaml
 apiVersion: keda.sh/v1alpha1

knowledge base/keybase.md

@@ -98,7 +98,7 @@ Under some circumnstances (like Docker or other containers) `root` can be the be
 
 ## Temporary devices
 
-Use `keybase oneshot` to establish a temporary device. The resulting process won't write credential information on the local storage disk nor it will make any changes to the user's sigchain; rather, it will hold the given paperkey in memory for as long as the corrisponding `keybase service` process is running or until `keybase logout` is called; when this happens, it will disappear.
+Use `keybase oneshot` to establish a temporary device. The resulting process won't write credential information on the local storage disk nor it will make any changes to the user's sigchain; rather, it will hold the given paperkey in memory for as long as the corresponding `keybase service` process is running or until `keybase logout` is called; when this happens, it will disappear.
 
 `keybase oneshot` needs a username and a paperkey to work, either passed in via standard input, command-line flags, or environment variables:
 

knowledge base/swap.md

@@ -16,7 +16,7 @@ sudo swapoff /dev/sda2
 sudo swapon -a
 sudo swapoff --all
 
-# chech what processes are swapping
+# check what processes are swapping
 # see the "si" (swap in) and "so" (swap out) columns
 vmstat
 vmstat --wide 1

knowledge base/sync.md

@@ -4,7 +4,7 @@
 # Flush all cached file data of the current user only.
 sync
 
-# Flush all pending write operations on all disks and mounted filesystems.
+# Flush all pending write operations on all disks and mounted file systems.
 sudo sync
 
 # Flush all pending write operations on given files only to disk.
@@ -23,7 +23,7 @@ sudo sync /dev/sdc1
 # Flush all pending write operations on all mounted filesystem from '/dev/sdb'.
 sudo sync /dev/sdb
 
-# Flush all pensing write operations on the entire file system which contains
+# Flush all pending write operations on the entire file system which contains
 # '/var/log/syslog'.
 sudo sync -f /var/log/syslog
 ```