summaryrefslogtreecommitdiff
path: root/capability.mdwn
diff options
context:
space:
mode:
authorArne Babenhauserheide <arne_bab@web.de>2011-12-19 06:28:18 +0100
committerArne Babenhauserheide <arne_bab@web.de>2011-12-19 06:28:18 +0100
commit83a6603ed188d746e2871decf85939fb7975b979 (patch)
tree5f671db8fa7e3828322a4d4b1b9cdce9b4bb6ac4 /capability.mdwn
parentd8b7944e910af3fdc1109846698d67738761f85a (diff)
parent6c057cff39ff782e9155c07eee44884cd9c48c9c (diff)
Merge branch 'master' of flubber:~hurd-web/hurd-web
Diffstat (limited to 'capability.mdwn')
-rw-r--r--capability.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/capability.mdwn b/capability.mdwn
index ddadf137..7219cdce 100644
--- a/capability.mdwn
+++ b/capability.mdwn
@@ -11,7 +11,7 @@ License|/fdl]]."]]"""]]
A capability is a protected reference. It is a reference in that
it designates an object; it is protected in that in cannot be
-forged. A capabilities both designates the object it refers to and
+forged. A capability both designates the object it refers to and
carries the authority to manipulate it.
By binding [[designation]] and [[authorization]] together, capabilities
@@ -25,7 +25,7 @@ to protect against A hijacking his authority. (This problem is
refused to the [[confused_deputy]] problem.) Also, since A likely
sent a string to identify the file to B, the identifier lacks a
[[naming_context]] and therefore may resolve to a different object
-than A intended. Be ensuring that [[designation]] and [[authorization]] are
+than A intended. By ensuring that [[designation]] and [[authorization]] are
always bound together, these problems are avoided.
Capability-based system architectures strive to meet the *principle of least
@@ -39,8 +39,8 @@ individually); attenuation design pattern, membranes
(wikipedia_object-capability_model)?
-->
-A capability mechanism is typically implemented in software my the operating
-system kernel (typically a [[microkernel]]. The computing cost (as compared to
+A capability mechanism is typically implemented in software by the operating
+system kernel (typically a [[microkernel]]). The computing cost (as compared to
a hardware implementation) is neglectable.