From 1f4787e7d7d3cf2a32befe642ae0163b653bead7 Mon Sep 17 00:00:00 2001 From: Adam Harvey Date: Mon, 19 Jul 2021 21:13:44 -0400 Subject: [PATCH] Fix typos --- content/_index.md | 4 ++-- content/getting-started/readfiles/framework-deploy-note.md_ | 2 +- content/kubernetes/best-practices/index.md | 2 +- content/kubernetes/deploying/index.md | 2 +- content/team/index.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/_index.md b/content/_index.md index 9868788..301e723 100755 --- a/content/_index.md +++ b/content/_index.md @@ -48,7 +48,7 @@ lives easier and work more efficiently. For example: * The [platform-deploy](https://github.com/cisco-sso/k8s-deploy) code pattern allows a user to enter a "cluster" directory and automatically have all - tools pre-configured for that specific enviroment. Thus, by opening + tools pre-configured for that specific environment. Thus, by opening multiple shells to different "cluster" directories the user may be configured to operate on several clusters simultaneously. This sounds simple, however it is not possible with "kubectl" today because only a @@ -57,6 +57,6 @@ lives easier and work more efficiently. For example: "platform-deploy" code pattern relies on [direnv](https://github.com/direnv/direnv) which is pre-configured in the [Kubernetes Development Kit (KDK)](https://github.com/cisco-sso/kdk), to - auto-magically set enviroment variables upon entering a cluster directory + auto-magically set environment variables upon entering a cluster directory and pull secrets from a [keybase](https://keybase.io/) team to properly configure all of the cloud tools such as kubectl, helm, aws-cli, etc. diff --git a/content/getting-started/readfiles/framework-deploy-note.md_ b/content/getting-started/readfiles/framework-deploy-note.md_ index 2e97545..f882e21 100644 --- a/content/getting-started/readfiles/framework-deploy-note.md_ +++ b/content/getting-started/readfiles/framework-deploy-note.md_ @@ -1,4 +1,4 @@ -[Framework-deploy](https://github.com/cisco-sso/framework-deploy) is a git repo which implments the KDF deployment +[Framework-deploy](https://github.com/cisco-sso/framework-deploy) is a git repo which implements the KDF deployment pattern. The boilerplate structure in framework-deploy is made to fit perfectly with the tools available in the KDK container. One may fork this repo as a basis for implementing the framework-deploy pattern for private kubernetes clusters. diff --git a/content/kubernetes/best-practices/index.md b/content/kubernetes/best-practices/index.md index a3c29f3..e8432e8 100644 --- a/content/kubernetes/best-practices/index.md +++ b/content/kubernetes/best-practices/index.md @@ -13,7 +13,7 @@ and thus can fit on any worker node. In addition, that pod is allowed to consum resources, allowing the risk of out of memory issues on the worker node causing instability and having the Linux OOM killer trigger and kill processes at random. -Guidlines for setting Pod Memory/Cpu Limits and Requests: +Guidelines for setting Pod Memory/Cpu Limits and Requests: * Set memory and cpu limits and requests are set on every pod * Set default memory and cpu limits on every namespace using diff --git a/content/kubernetes/deploying/index.md b/content/kubernetes/deploying/index.md index 51c3667..b59fd88 100644 --- a/content/kubernetes/deploying/index.md +++ b/content/kubernetes/deploying/index.md @@ -31,7 +31,7 @@ functionality. worker node. Its persistent volume is local to a node and cannot be network mounted on a different worker node. This drastically decreases the resilience of any stateful application in Kubernetes upon node failures. * Load-balancer integration - * Without this, applications within kubernetes will not be auto-wired to be reachable from outside of kuberentes. + * Without this, applications within kubernetes will not be auto-wired to be reachable from outside of Kubernetes. There are less resilient and unpalatable workarounds for the above, for example: diff --git a/content/team/index.md b/content/team/index.md index 255f892..29380c3 100644 --- a/content/team/index.md +++ b/content/team/index.md @@ -52,7 +52,7 @@ At minimum: ## Upstreaming -If you modify an open-source project, make the effort to submit an upsteam PR and get your code merged. +If you modify an open-source project, make the effort to submit an upstream PR and get your code merged. This eliminates the long term burden of maintaining forked code, thus reducing costs for your business. It also is important to contribute to the open-source community.