summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorScott Konzem <konzems@gmail.com>2015-06-05 11:35:17 -0400
committerScott Konzem <konzems@gmail.com>2015-06-05 11:35:17 -0400
commit1bb3ed53eeed2d0cc493f7974b09e4168c35ad9f (patch)
tree22a308a944029c049001ee28b8e16630be6276b1
parentbd8e7d842472ad28f3b56e6a425939ad48a1274d (diff)
Fix misspellings in documentation
-rw-r--r--secrets.md2
-rw-r--r--service_accounts.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/secrets.md b/secrets.md
index cbf93ee2..0bacb8d4 100644
--- a/secrets.md
+++ b/secrets.md
@@ -122,7 +122,7 @@ We should consider what the best way to allow this is; there are a few different
3. Give secrets attributes that allow the user to express that the secret should be presented to
the container as an environment variable. The container's environment would contain the
- desired values and the software in the container could use them without accomodation the
+ desired values and the software in the container could use them without accommodation the
command or setup script.
For our initial work, we will treat all secrets as files to narrow the problem space. There will
diff --git a/service_accounts.md b/service_accounts.md
index 9e6bc099..72a10207 100644
--- a/service_accounts.md
+++ b/service_accounts.md
@@ -149,7 +149,7 @@ First, if it finds pods which have a `Pod.Spec.ServiceAccountUsername` but no `P
then it copies in the referenced securityContext and secrets references for the corresponding `serviceAccount`.
Second, if ServiceAccount definitions change, it may take some actions.
-**TODO**: decide what actions it takes when a serviceAccount defintion changes. Does it stop pods, or just
+**TODO**: decide what actions it takes when a serviceAccount definition changes. Does it stop pods, or just
allow someone to list ones that out out of spec? In general, people may want to customize this?
Third, if a new namespace is created, it may create a new serviceAccount for that namespace. This may include