Change from 'advanced' to 'filtered', already in published -00

netmod-wg · Jan 16, 2020 · d3fb1de · d3fb1de
1 parent 2fbf4de
commit d3fb1de
Showing 1 changed file with 8 additions and 10 deletions.
diff --git a/yang-schema-comparison/draft-verdt-netmod-yang-schema-comparision.xml b/yang-schema-comparison/draft-verdt-netmod-yang-schema-comparision.xml
@@ -223,19 +223,17 @@
      implemented modules revision history (or YANG semantic version number if
      used to identify module revisions).</t>
    </section>
-   <section anchor="advanced_schema_comparison_algorithm" title="Advanced YANG schema comparison algorithm">
-     <t>A more accurate method to compare YANG schema, that is less likely to
-     report inconsequential differences, is to construct full schema trees for
-     the two schema versions, and then directly apply a version of the
-     comparison algorithm defined in <xref
-     target="generic_comparison_algorithm"/>.  This may be particular useful
-     when the schema represents a complete datastore schema for a server because
-     it allows various refinements to the comparison algorithm to provide a more
-     specific answer about what changes may impact a particular client.</t>
+   <section anchor="advanced_schema_comparison_algorithm" title="Filtered YANG schema comparison algorithm">
+     <t>Another method to compare YANG schema, that is less likely to report inconsequential differences, is to
+     construct full schema trees for the two schema versions, directly apply a version of the comparison
+     algorithm defined in <xref target="generic_comparison_algorithm"/>.  This may be
+     particular useful when the schema represents a complete datastore schema for a server because it allows various
+     filtered to the comparison algorithm to provide a more specific answer about what changes may impact a
+     particular client.</t>
      <t>The full schema tree can easily be constructed from a YANG package
      definition, or alternative YANG schema definition.</t>
      <t>Controlled by input parameters to the comparison algorithm, the
-     following parts of the schema trees can optionally be ignored during the
+     following parts of the schema trees can optionally be filtered during the
      comparison:
      <list>
        <t>All "grouping" statements can be ignored (after all "use" statements