Updates CHANGELOG

CHANGELOG.md

@@ -25,22 +25,20 @@ Thank you to all who have contributed!
 
 ## [0.14.9]
 
-### Added
-
 ### Changed
 - With full, closed schema, the planner will now give a plan-time warning when it can prove an exclude path will never 
 exclude a value (relevant issue -- https://github.com/partiql/partiql-lang/issues/91).
 
-### Deprecated
-
-### Fixed
-
-### Removed
-
-### Security
+### Experimental Changes
+- **BREAKING**: For the _experimental_ `org.partiql.lang.domains` of `PartiqlLogical`, `PartiqlLogicalResolved`, and `PartiqlPhysical`,
+the modeling of DML has changed substantially. These changes, while considered breaking changes, are part of an
+experimental area of the PartiQL library and thus do not mandate a major-version bump of this library. Consumers
+of these experimental APIs should be wary of these changes.
 
 ### Contributors
 - @alancai98
+- @dlurton
+- @johnedquinn
 
 ## [0.14.8]
 

partiql-ast/src/main/pig/partiql.ion

@@ -808,7 +808,7 @@ may then be further optimized by selecting better implementations of each operat
                   // An `INSERT` DML operation, which is fundamentally different from UPDATE and DELETE
                   // because it lacks a FROM and WHERE clause while also including an ON CONFLICT clause.
                   //
-                  // Models: INSERT INTO <dml_target> [AS <target_alias>] <rows_to_isnert> [<on-conflict>]
+                  // Models: INSERT INTO <dml_target> [AS <target_alias>] <rows_to_insert> [<on-conflict>]
                   (dml_insert
                       // The target is an expression indicates the table whose data is to be manipulated.
                       // With current PartiQL Parser `SqlParser`, this can be an identifier or a simplified path expression