fix documentation typo

nmggithub · nmggithub · commit adc8428cb04e · 2024-11-22T23:05:14.000-05:00
diff --git a/Sources/Mach/Core/Core.docc/Architecture.md b/Sources/Mach/Core/Core.docc/Architecture.md
@@ -21,4 +21,4 @@ Additionally:
 
 ## On "Port Names"
 
-In many cases, some rights to the same port will carry the same name in a task's name space. Traditionally, if a task held both a send right and a receive right to a port, both rights would have the same name. In fact, if the task held multiple references to each, they all would have the same name. This behavior of sharing names appears to still be the current behavior to this day. While there are other rights (such as the **send one right**) which may be named differently, this name-sharing of the core rights makes the "port name" term make a bit more sense.
+In many cases, some rights to the same port will carry the same name in a task's name space. Traditionally, if a task held both a send right and a receive right to a port, both rights would have the same name. In fact, if the task held multiple references to each, they all would have the same name. This behavior of sharing names appears to still be the current behavior to this day. While there are other rights (such as the **send-once right**) which may be named differently, this name-sharing of the core rights makes the "port name" term make a bit more sense.

Original file line number	Diff line number	Diff line change
`@@ -21,4 +21,4 @@ Additionally:`
`21`	`21`
`22`	`22`	`## On "Port Names"`
`23`	`23`
`24`		-In many cases, some rights to the same port will carry the same name in a task's name space. Traditionally, if a task held both a send right and a receive right to a port, both rights would have the same name. In fact, if the task held multiple references to each, they all would have the same name. This behavior of sharing names appears to still be the current behavior to this day. While there are other rights (such as the send one right) which may be named differently, this name-sharing of the core rights makes the "port name" term make a bit more sense.
	`24`	+In many cases, some rights to the same port will carry the same name in a task's name space. Traditionally, if a task held both a send right and a receive right to a port, both rights would have the same name. In fact, if the task held multiple references to each, they all would have the same name. This behavior of sharing names appears to still be the current behavior to this day. While there are other rights (such as the send-once right) which may be named differently, this name-sharing of the core rights makes the "port name" term make a bit more sense.