Update incremental insert overwrite docs (#331)

* update README.md file to indicate that insert_overwrite is

* update CHANGELOG.md

* fix typo

* reframe the documentation

CHANGELOG.md

@@ -1,3 +1,8 @@
+### Release XXXXX
+#### Improvements
+* Added a new *experimental* incremental strategy - `insert_overwrite` was added which replaces existing data in a target table partition by partition, ensuring only the specified partitions are overwritten with new data, which helps maintain performance and data consistency. This feature was not tested with distribution models and might not work with such materializations.  
+
+
 ### Release [1.8.1], 2024-07-11
 #### Bug Fix
 * Refresh materialized_view table only if `--full-refresh` is specified.

README.md

@@ -185,8 +185,10 @@ This strategy replaces the `inserts_only` setting in previous versions of dbt-cl
 As a result duplicate rows are not eliminated, and there is no temporary or intermediate table.  It is the fastest approach if duplicates are either permitted
 in the data or excluded by the incremental query WHERE clause/filter.
 
-### The insert_overwrite Strategy
-
+### The insert_overwrite Strategy (Experimental)
+> [IMPORTANT]  
+> Currently, the insert_overwrite strategy is not fully functional with distributed materializations. 
+ 
 Performs the following steps:
 1. Create a staging (temporary) table with the same structure as the incremental model relation: `CREATE TABLE <staging> AS <target>`.
 2. Insert only new records (produced by `SELECT`) into the staging table.