diff --git a/ALLOF.md b/ALLOF.md
index c7eb9217..74998179 100644
--- a/ALLOF.md
+++ b/ALLOF.md
@@ -11,7 +11,7 @@ Consider, for example, the following comparison of two OpenAPI specs:
 oasdiff breaking data/allof/simple.yaml data/allof/revision.yaml 
 ```
 
-The result shows one breaking change which is due to a new subschema that was added under anyOf. But the new subschema, doesn't actually add any new constraints, because it is identical to a previously existing subschema, and, as such, this isn't a breaking chanage.
+The result shows one breaking change which is due to a new subschema that was added under allOf. But the new subschema, doesn't actually add any new constraints, because it is identical to a previously existing subschema, and, as such, this isn't a breaking chanage.
 You can verify this with a regular diff comparison:
 ```
 diff --side-by-side data/allof/simple.yaml data/allof/revision.yaml
@@ -29,7 +29,6 @@ In order to see how oasdiff merges allOf, you can use the dedicated `flatten` co
 oasdiff flatten data/allof/simple.yaml
 ```
 
-Limitations:
 The following schema fields are not merged:
 - Extensions
 - Default