summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/libdiskfs_locking.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/libdiskfs_locking.mdwn')
-rw-r--r--community/gsoc/project_ideas/libdiskfs_locking.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/libdiskfs_locking.mdwn b/community/gsoc/project_ideas/libdiskfs_locking.mdwn
index 2a08b387..570a9581 100644
--- a/community/gsoc/project_ideas/libdiskfs_locking.mdwn
+++ b/community/gsoc/project_ideas/libdiskfs_locking.mdwn
@@ -18,8 +18,8 @@ faulty paths causing these lockups.
The task is systematically checking the [[hurd/libdiskfs]] code for this kind of locking
issues. To achieve this, some kind of test harness has to be implemented: For
-exmple instrumenting the code to check locking correctness constantly at
-runtime. Or implementing a unit testing framework that explicitely checks
+example instrumenting the code to check locking correctness constantly at
+runtime. Or implementing a unit testing framework that explicitly checks
locking in various code paths. (The latter could serve as a template for
implementing unit checks in other parts of the Hurd codebase...)