Merge branch 'master' into create-pull-request/patch

Author: deepakunni3

principles/fp-002-format.md

@@ -7,7 +7,7 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
 
 ## Summary
 
-The ontology is made available in a common formal language in an accepted concrete syntax.
+The ontology MUST be made available in a common formal language in an accepted concrete syntax.
 
 ## Purpose
 

principles/fp-004-versioning.md

@@ -7,7 +7,7 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
 
 ## Summary
 
-The ontology provider has documented procedures for versioning the ontology, and different versions of ontology are marked, stored, and officially released.
+The ontology provider MUST have documented procedures for versioning the ontology, and different versions of ontology MUST be marked, stored, and officially released.
 
 ## Purpose
 

principles/fp-005-delineated-content.md

@@ -10,7 +10,7 @@ The wording of this principle is still in progress, with some issues still to be
 
 ## Summary
 
-The scope of an ontology is the extent of the domain or subject matter it intends to cover. The ontology must have a clearly specified scope and content that adheres to that scope.
+The scope of an ontology is the extent of the domain or subject matter it intends to cover. The ontology MUST have a clearly specified scope and content that adheres to that scope.
 
 ## Purpose