summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGin <hejin@ghostcloud.cn>2017-11-14 11:30:36 +0800
committerGitHub <noreply@github.com>2017-11-14 11:30:36 +0800
commite81f02c0f0aa1b7240b980e900c1c051a7aca099 (patch)
tree9165f145a47cd7f53c951514ab93c2d6892c20fb
parent62f13139cab5369fbbf6dc611ad72029e768ca84 (diff)
Update propagation.md
-rw-r--r--contributors/design-proposals/node/propagation.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/propagation.md b/contributors/design-proposals/node/propagation.md
index 3c665552..959e69f9 100644
--- a/contributors/design-proposals/node/propagation.md
+++ b/contributors/design-proposals/node/propagation.md
@@ -294,7 +294,7 @@ may not propagate back to the host, depending of ordering of mount operations)
1. limitations this imposes on runtimes (RO-remounting may now affects the host,
is it on purpose or a dangerous side-effect?)
-1. A shared mount target imposes some costraints on its parent subtree (generally,
+1. A shared mount target imposes some constraints on its parent subtree (generally,
it has to be shared as well), which in turn prevents some mount operations when
preparing a pod (eg. MS_MOVE).