Update MP Design Rules.md

Author: pchemguy

MP Design Rules.md

@@ -18,7 +18,7 @@ This project explores SQLite capacity and features for managing hierarchical sys
  7. Any categorized item may be assigned multiple categories.
  8. No category-item name collision.
 
-It is instructive to compare and contrast systems described by these rules with file systems (FS), probably the most familiar hierarchical structures for the organization of file system objects (FSO), particularly files. Like directories organize files, categories facilitate the organization of categorized items. A large portion of the above rules governs naming conventions, some of which are similar to those of FSs, while others may appear counterintuitive. Fundamental differences between the two systems justify the latter choices. For once, while categories and categorized objects belong to separate object spaces (database tables), directories and files share the same namespace. Also, categories are closer to selection filters than surrogate containers, so category assignment is akin to tagging rather than placing objects in folder-like bins/containers and does not cause any object relocation, physical or virtual. With these differences in mind, let us provide some justification for the selected rules.
+It is instructive to compare and contrast systems described by these rules with file systems (FS), probably the most familiar hierarchical structures for the organization of file system objects (FSO), particularly files. Like directories organize files, categories facilitate the organization of categorized items. A large portion of the above rules governs naming conventions, some of which are similar to those of FSs, while others may appear counterintuitive. Fundamental differences between the two systems justify the latter choices. For once, categories and categorized items belong to separate object spaces (database tables), whereas directories and files share the same namespace. Also, categories act more like selection filters than surrogate containers. Therefore, category assignment is akin to tagging rather than placing items in folder-like bins/containers (no item relocation, physical or virtual). With these differences in mind, let us discuss the rationale behind individual rules.
 
 #### Rule #1
 
@@ -38,7 +38,7 @@ This rule is essentially common sense. Many broadly used classification systems
 
 #### Rule #5
 
-Each category is associated with a distinct classification feature (encoded in the category's path, see Rule #4) used to identify a subset of objects sharing the same feature. Allowing sibling namesakes among categories is, therefore, meaningless and degrades, if not breaks, the utility of the classification system (cf. with FS paths, which identify FSOs). Because of this rule, the *path* column constitutes a natural primary key and is a suitable reference for foreign key relationships. Also, category subtree COPY/MOVE operations may cause name conflicts, and the processing script should partially follow FS logic (see following sections for further discussion). For each conflict, only a single conflicting node remians, retaining item assignments from both conflicitng nodes.
+Each category is associated with a distinct classification feature (encoded in the category's path, see Rule #4) used to identify a subset of objects sharing the same feature. Allowing sibling namesakes among categories is, therefore, meaningless and degrades, if not breaks, the utility of the classification system (cf. with FS paths, which identify FSOs). Because of this rule, the *path* column constitutes a natural primary key and is a suitable reference for foreign key relationships. Also, category subtree COPY/MOVE operations may cause name conflicts, and the processing script should partially follow FS logic (see general notes above and following sections for further discussion). Only a single node remains for each conflicting pair, retaining item assignments from both nodes.
 
 #### Rule #6