summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-12 03:52:14 +0100
committerantrik <antrik@users.sf.net>2009-03-12 09:16:57 +0100
commit49fbd30e4a54c687530b9a3566d1463e5f638ddc (patch)
tree083021bcf6e3bb4c430fd18bdd2cb7caa09af3a2 /community/gsoc/project_ideas
parent8528972b69b105c5e965779ec0a797162a109b57 (diff)
mtab GSoC task: fix typos
Diffstat (limited to 'community/gsoc/project_ideas')
-rw-r--r--community/gsoc/project_ideas/mtab.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/mtab.mdwn b/community/gsoc/project_ideas/mtab.mdwn
index 056ed042..99b37655 100644
--- a/community/gsoc/project_ideas/mtab.mdwn
+++ b/community/gsoc/project_ideas/mtab.mdwn
@@ -26,10 +26,10 @@ explicitely specified mountpoints, instead of displaying the usual listing.
One possible solution to this would be for the translator startup mechanism to
update the `mtab` on any `mount`/`unmount`, like in traditional systems.
-However, there are same problems with this approach. Most notably: what to do
+However, there are some problems with this approach. Most notably: what to do
with passive translators, i.e., translators that are not presently running, but
set up to be started automatically whenever the node is accessed? Probably
-these should be counted an among the mounted filesystems; but how to handle the
+these should be counted among the mounted filesystems; but how to handle the
`mtab` updates for a translator that is not started yet? Generally, being
centralized and event-based, this is a pretty unelegant, non-hurdish solution.