M15-Release-Notes.md

@@ -191,13 +191,8 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha
   * `application.yml` has been renamed to `application-local.yml`
 * Ignite Cache Name
   * We now require a separate identifying string for the name of a cache, as configured in either `application-local.yml`, `application-remote.yml`, or `application-k8s-remote.yml`
-    * Each kind previously needed to contain the `name` and `chronExpr` properties, but now must contain a `cacheName` property:
-
-      <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>
-
-      </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.
+    * Each kind previously needed to contain the `name` and `chronExpr` properties, but now must contain a `cacheName` property
+      * 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