being a little less assertive

partly addressing #35 (comment)

registries/draft-wilde-registries-02.xml

@@ -118,7 +118,7 @@
             <t>The levels often carry differentiations in a variety of factors, such as how established represented concepts are, how well and/or how open they are documented, how the expected stability of the entry is, and what level of scrutiny is applied during the review process when registering a new value. Specifications have a wide latitude defining those levels and specifying what they represent and how they affect value semantics and registration procedures.</t>
             <t>As one example, media types <xref target="RFC6838"/> establish a "standards tree" and as well as other trees ("vendor" and "personal"). Entries in these trees are distinguished by prefix or lack thereof. The general idea is that the non-standard trees contain entries that are not quite at the same level, significance-wise, as the standards tree.</t>
             <t>As another example, URI schemes <xref target="RFC7595"/> differentiate registrations into "permanent" and "provisional" schemes. In addition, URI schemes can also be registered as being "historical". A "provisional" registration is intended to be used in cases where URI deployment is likely to happen outside of a private environment, but still controlled by a private party. It is also possible to update a registration from "provisional" to "permanent" once the associated protocol has become stable or more widely deployed.</t>
-            <t>The classification of registry entries into "permanent" and "provisional" is a pattern being followed by other IETF specifications and registries as well, for example by the registration procedures for message header fields <xref target="RFC3864"/>.</t>
+            <t>The classification of registry entries into "permanent" and "provisional" is a pattern being followed by some IETF specifications and registries as well, for example by the registration procedures for message header fields <xref target="RFC3864"/>.</t>
          </section>
          <section title="Separation by Value Syntax" anchor="value-syntax">
             <t>While the examples given in <xref target="levels"/> sometimes use ways to differentiate entry levels by name, this is just a convenience so that it is possible to determine a value's level by value syntax. In this case, the value syntax is enforced by registration policy, meaning that during the registration process it is ensured that when a registration request for a certain level is made, the registered value conforms to the required syntax. However, in this case, all values still need to be registered.</t>