summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/secure_chroot.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/secure_chroot.mdwn')
-rw-r--r--community/gsoc/project_ideas/secure_chroot.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/community/gsoc/project_ideas/secure_chroot.mdwn b/community/gsoc/project_ideas/secure_chroot.mdwn
index 0a08bbf5..feb30a7c 100644
--- a/community/gsoc/project_ideas/secure_chroot.mdwn
+++ b/community/gsoc/project_ideas/secure_chroot.mdwn
@@ -16,10 +16,10 @@ good, as it allows easily escaping the `chroot`, for example by use of
[[passive_translators|hurd/translator]].
Many solutions have been suggested for this problem -- ranging from simple
-workaround changing the behaviour of passive translators in a `chroot`;
-changing the context in which passive translators are exectuted; changing the
+workaround changing the behavior of passive translators in a `chroot`;
+changing the context in which passive translators are executed; changing the
interpretation of filenames in a chroot; to reworking the whole passive
-translator mechanism. Some involving a completely different approch to
+translator mechanism. Some involving a completely different approach to
`chroot` implementation, using a proxy instead of a special system call in the
filesystem servers.