change readme examples to match the post-spec/more-keys world

libuconf · Mar 15, 2021 · 2523f04 · 2523f04
1 parent 23818bd
commit 2523f04
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -137,4 +137,4 @@ Both of these are correct, and neither is preferred.
 
 * `core`: compliant.
 * `ini`: compliant.
-* `ext`: flexspace, tabulation.
+* `ext`: none.
diff --git a/tests/README.md b/tests/README.md
@@ -36,9 +36,9 @@ If you are writing an implementation, please describe its compliance as follows:
 3. Compliance for `ext` per-feature (list out every extension (basename of the files) that you are conformant to).
 
 For example:
-* `core`: 32/32, `ini`: compliant, `ext`: flexspace, tabulation.
+* `core`: 29/29, `ini`: compliant, `ext`: more-keys.
 * `core`: compliant, `ini`: non-compliant, `ext`: none.
-* `core`: 24/32, `ini`: compliant, `ext`: flexspace.
+* `core`: 24/29, `ini`: compliant, `ext`: more-keys.
 
 Obviously, any implementation that is not fully core compliant should not be considered finished.