M15-Release-Notes.md

@@ -197,9 +197,13 @@ 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 cacheName: osdu_wks_master-data--Well_1.0.0 chronExpr: 0 0 8  ?`</span>
+      <span dir="">- </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.
+      <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.
       * 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