M15-Release-Notes.md

@@ -65,8 +65,6 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha
 
 ### GCZ (Geospatial Consumption Zone)
 
-#### New Features
-
 * **Ingestion**
   * Transformer now supports limited Ingestion of `WellLog` records via ID-to-ID spatialization
     * Example: Store Well Logs to Ignite **as Well Surface Locations only** with Well Log attributes - then view on a map
@@ -197,9 +195,9 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha
 
       <pre>
 
-      <span dir="">- name: osdu:wks:master-data--Well:1.0.0 </span>\\ <span dir="">cacheName: osdu_wks_master-data--Well_1.0.0 </span>\\ <span dir="">chronExpr: 0 0 8 ?</span>
+      <span dir="">- name: osdu:wks:master-data--Well:1.0.0 </span>\\\\ <span dir="">cacheName: osdu_wks_master-data--Well_1.0.0 </span>\\\\ <span dir="">chronExpr: 0 0 8 ?</span>
 
-      </pre>\\\* The reason for this change is due to our new support of Persistence-Enabled Ignite Clusters, which strictly impose that cache names do not contain special characters such as \\\`:\\\` due to conflicts with file storage. Please note that taking the kind name and simply replacing all \\\`:\\\` characters with an underscore \\\`\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\_\\\` should work fine, but you are welcome to name your caches however you like, avoiding special characters.
+      </pre>\\\\\\\* The reason for this change is due to our new support of Persistence-Enabled Ignite Clusters, which strictly impose that cache names do not contain special characters such as \\\\\\\`:\\\\\\\` due to conflicts with file storage. Please note that taking the kind name and simply replacing all \\\\\\\`:\\\\\\\` characters with an underscore \\\\\\\`\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\_\\\\\\\` should work fine, but you are welcome to name your caches however you like, avoiding special characters.
       * Additionally, you will need to configure `koop-config.json` to include the `cacheName` property or else the Provider will be unable to find the cache by `kind` entity alone.
 
 ## Known Issues/Gaps