summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--community/gsoc/project_ideas/driver_glue_code.mdwn2
-rw-r--r--community/gsoc/project_ideas/dtrace.mdwn2
-rw-r--r--community/gsoc/project_ideas/gnumach_cleanup.mdwn2
3 files changed, 3 insertions, 3 deletions
diff --git a/community/gsoc/project_ideas/driver_glue_code.mdwn b/community/gsoc/project_ideas/driver_glue_code.mdwn
index 4e1e338c..9c063e9f 100644
--- a/community/gsoc/project_ideas/driver_glue_code.mdwn
+++ b/community/gsoc/project_ideas/driver_glue_code.mdwn
@@ -12,7 +12,7 @@ is included in the section entitled
[[!meta title="New Driver Glue Code"]]
Although a driver framework in user space would be desirable, presently the Hurd
-uses kernel drivers in the micro kernel,
+uses kernel drivers in the microkernel,
[[GNU_Mach|microkernel/mach/gnumach]]. (And changing this would be far beyond a
GSoC project...)
diff --git a/community/gsoc/project_ideas/dtrace.mdwn b/community/gsoc/project_ideas/dtrace.mdwn
index 25e6db29..4a46cf38 100644
--- a/community/gsoc/project_ideas/dtrace.mdwn
+++ b/community/gsoc/project_ideas/dtrace.mdwn
@@ -18,7 +18,7 @@ causes bad performance is necessary to improve the situation.
For that, we need tools for performance measurements. While all kinds of more
or less specific profiling tools could be conceived, the most promising and
generic approach seems to be a framework for logging certain events in the
-running system (both in the micro kernel and in the Hurd servers). This would
+running system (both in the microkernel and in the Hurd servers). This would
allow checking how much time is spent in certain modules, how often certain
situations occur, how things interact, etc. It could also prove helpful in
debugging some issues that are otherwise hard to find because of complex
diff --git a/community/gsoc/project_ideas/gnumach_cleanup.mdwn b/community/gsoc/project_ideas/gnumach_cleanup.mdwn
index 954e1242..4aef0d1b 100644
--- a/community/gsoc/project_ideas/gnumach_cleanup.mdwn
+++ b/community/gsoc/project_ideas/gnumach_cleanup.mdwn
@@ -10,7 +10,7 @@ is included in the section entitled
[[!meta title="GNU Mach Code Cleanup"]]
-Although there are some attempts to move to a more modern micro kernel
+Although there are some attempts to move to a more modern microkernel
altogether, the current Hurd implementation is based on
[[GNU_Mach|microkernel/mach/gnumach]], which is only a slightly modified
variant of the original CMU [[microkernel/Mach]].