diff options
| author | Carl Fredrik Hammar <hammy.lite@gmail.com> | 2010-03-10 16:19:06 +0100 |
|---|---|---|
| committer | Carl Fredrik Hammar <hammy.lite@gmail.com> | 2010-03-10 16:19:06 +0100 |
| commit | 6eb6d5314e303379debbef82921a215ef2b00d98 (patch) | |
| tree | 55536b9636dc3ccfaf7829c96940774a13cf49e3 /community/gsoc/project_ideas/libdiskfs_locking.mdwn | |
| parent | 5a615978181a1b8d85326d8cf3137ed4b0b46bf7 (diff) | |
Fix typos and spelling on GSoC pages
Diffstat (limited to 'community/gsoc/project_ideas/libdiskfs_locking.mdwn')
| -rw-r--r-- | community/gsoc/project_ideas/libdiskfs_locking.mdwn | 4 |
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...) |