@@ -90,14 +90,13 @@ between data and code and its use is growing in popularity.
9090An example of structured code is provided by GitHub with its workflow
9191specification files. They use YAML _. Unfortunately, the syntax of the code
9292snippets held in the various fields can be confused with *YAML * syntax, which
93- leads to unnecessary errors, confusion, and complexity (see :ref: `YAML issues
94- <vs_yaml>`). JSON _ suffers from similar problems. *NestedText * excels for
95- these applications as it holds code snippets without any need for quoting or
96- escaping. *NestedText * provides simple unambiguous rules for defining the
97- structure of your data and when these rules are followed there is no way for any
98- syntax or special characters in the values of your data to be confused with
99- *NestedText * syntax. In fact, it is possible for *NestedText * to hold
100- *NestedText * snippets without conflict.
93+ leads to unnecessary errors, confusion, and complexity. JSON _ suffers from
94+ similar problems. *NestedText * excels for these applications as it holds code
95+ snippets without any need for quoting or escaping. *NestedText * provides simple
96+ unambiguous rules for defining the structure of your data and when these rules
97+ are followed there is no way for any syntax or special characters in the values
98+ of your data to be confused with *NestedText * syntax. In fact, it is possible
99+ for *NestedText * to hold *NestedText * snippets without conflict.
101100
102101Another example of structured code is provided by the files that contain the
103102test cases used by `Parametrize From File `_, a PyTest _ plugin.
0 commit comments