web commit by http://vininim.myopenid.com/: something wrong with numbered list processing, using this temp

1 files changed, 4 insertions, 4 deletions

diff --git a/NextHurd/Part1OwnershipAndContracts.mdwn b/NextHurd/Part1OwnershipAndContracts.mdwn
index a5260bc6..7be1ec05 100644
--- a/NextHurd/Part1OwnershipAndContracts.mdwn
+++ b/NextHurd/Part1OwnershipAndContracts.mdwn
@@ -8,17 +8,17 @@ Let me jump right in at the technical level: I claim that every relationship bet
 
 ## <a name="Process_Relationship_Categories"> Process Relationship Categories </a>
 
-0. It is not possible for the processes to communicate via direct IPC.
+* 0 - It is not possible for the processes to communicate via direct IPC.
 
 In all other categories, it is possible for the processes to communicate via direct IPC, because one of the processes, let me call it process A, has a capability to the other process, let me call it B.
 
-1. The collective authority of process B, immediately[1] after the time it was instantiated, is necessarily a strict subset of the collective authority hold by process A at that time.
+* 1 - The collective authority of process B, immediately[1] after the time it was instantiated, is necessarily a strict subset of the collective authority hold by process A at that time.
 
 [1] See my challenge-email to find a definition of the window of time that gives meaning to the word "immediately" in the case where process B is instantiated indirectly or directly because of an action in process A. If process B is instantiated independent of process A, just assume that the collective authority hold by process A is the empty set.
 
-2. The set of collective authority of process B, immediately after the time it was instantiated, minus the collective authority of process A (if it existed), is necessarily not empty. Some of the capabilities in this non-empty set provide the ability to write-out.
+* 2 - The set of collective authority of process B, immediately after the time it was instantiated, minus the collective authority of process A (if it existed), is necessarily not empty. Some of the capabilities in this non-empty set provide the ability to write-out.
 
-3. The set of collective authority of process B, immediately after the time it was instantiated, minus the collective authority of process A (if it existed), is necessarily not empty. None of the capabilities in this non-empty set provide the ability to write-out.
+* 3 - The set of collective authority of process B, immediately after the time it was instantiated, minus the collective authority of process A (if it existed), is necessarily not empty. None of the capabilities in this non-empty set provide the ability to write-out.
 
 This categorization does not say anything about encapsulation. However, it is to be understood from the description that in category 0, 2 and 3, process B is encapsulated. If it were not, the collective authority that is hold by A would include the authority of B by transition. In category 1, it is to be understood that process B, in principle, can not be successfully encapsulated (to see this, pay attention to the fact that process A could pre-arrange its authority so that no capability it has provides the possibility for encapsulation).