fix: Use AST to replace notes & warnings.

docs/config/8.6.0_docs.md

@@ -52,10 +52,8 @@ Implementors can only modify configurations using directives, and cannot change
 
 The Two types of directives: are `init` (or `initialize`) and `wrap`.
 
-> **Note**\
+> **Note**
 > All directives are enclosed in `%%{ }%%`
->
-> >
 
 Older versions of mermaid will not parse directives because `%%` will comment out the directive. This makes the update backwards-compatible.
 
@@ -67,7 +65,7 @@ Older versions of mermaid will not parse directives because `%%` will comment ou
 | --------- | ----------------------- | --------- | -------- | ----------------------------------------------- |
 | init      | modifies configurations | Directive | Optional | Any parameters not included in the secure array |
 
-> **Note**\
+> **Note**
 > init would be an argument-directive: `%%{init: { **insert argument here**}}%%`
 >
 > The json object that is passed as {**argument** } must be valid, quoted json or it will be ignored.
@@ -78,8 +76,6 @@ Older versions of mermaid will not parse directives because `%%` will comment ou
 > Configurations that are passed through init cannot change the parameters in a secure array at a higher level. In the event of a collision, mermaid will give priority to secure arrays and parse the request without changing the values of those parameters in conflict.
 >
 > When deployed within code, init is called before the graph/diagram description.
->
-> >
 
 **for example**:
 
@@ -113,7 +109,7 @@ Older versions of mermaid will not parse directives because `%%` will comment ou
 | --------- | ----------------------------- | --------- | -------- | ---------- |
 | wrap      | a callable text-wrap function | Directive | Optional | %%{wrap}%% |
 
-> **Note**\
+> **Note**
 > Wrap is a function that is currently only deployable for sequence diagrams.
 >
 > `Wrap respects a manually added <br>, so if the user wants to break up their text, they have full control over line breaks by adding <br> tags.`
@@ -121,8 +117,6 @@ Older versions of mermaid will not parse directives because `%%` will comment ou
 > It is a non-argument directive and can be executed thusly:
 >
 > `%%{wrap}%%` .
->
-> >
 
 **An example of text wrapping in a sequence diagram**:
 
@@ -164,14 +158,12 @@ Example of **object.Assign**:
 | --------------- | ------------------------------------- | ----------- | --------------------------------------- | ---------- | ---------- |
 | `setSiteConfig` | Sets the siteConfig to desired values | Put Request | Any Values, except ones in secure array | conf       | siteConfig |
 
-> **Note**\
+> **Note**
 > Sets the siteConfig. The siteConfig is a protected configuration for repeat use. Calls to reset() will reset
 > the currentConfig to siteConfig. Calls to reset(configApi.defaultConfig) will reset siteConfig and currentConfig
 > to the defaultConfig
 > Note: currentConfig is set in this function。
 > Default value: will mirror Global Config
->
-> >
 
 ## getSiteConfig
 
@@ -179,10 +171,8 @@ Example of **object.Assign**:
 | --------------- | --------------------------------------------------- | ----------- | ---------------------------------- |
 | `getSiteConfig` | Returns the current `siteConfig` base configuration | Get Request | Returns Any Values in `siteConfig` |
 
-> **Note**\
+> **Note**
 > Returns any values in siteConfig.
->
-> >
 
 ## setConfig
 
@@ -190,12 +180,10 @@ Example of **object.Assign**:
 | ----------- | ------------------------------------------ | ----------- | --------------------------------- | ---------- | ---------------------------------------------- |
 | `setConfig` | Sets the `currentConfig` to desired values | Put Request | Any Values, those in secure array | conf       | `currentConfig` merged with the sanitized conf |
 
-> **Note**\
+> **Note**
 > Sets the currentConfig. The parameter conf is sanitized based on the siteConfig.secure keys. Any
 > values found in conf with key found in siteConfig.secure will be replaced with the corresponding
 > siteConfig value.
->
-> >
 
 ## getConfig
 
@@ -203,10 +191,8 @@ Example of **object.Assign**:
 | ----------- | --------------------------- | ----------- | ------------------------------- |
 | `getConfig` | Obtains the `currentConfig` | Get Request | Any Values from `currentConfig` |
 
-> **Note**\
+> **Note**
 > Returns any values in currentConfig.
->
-> >
 
 ## sanitize
 
@@ -214,11 +200,9 @@ Example of **object.Assign**:
 | ---------- | ---------------------------------------- | -------------- | ------ |
 | `sanitize` | Sets the `siteConfig` to desired values. | Put Request(?) | None   |
 
-> **Note**\
+> **Note**
 > modifies options in-place
 > Ensures options parameter does not attempt to override siteConfig secure keys.
->
-> >
 
 ## reset
 
@@ -232,9 +216,7 @@ Example of **object.Assign**:
 | --------- | ------------------------------------------------------------ | ---------- | -------- | -------------------------------------------- |
 | `conf`    | base set of values, which `currentConfig` could be reset to. | Dictionary | Required | Any Values, with respect to the secure Array |
 
-> **Note**\
+> **Note**
 > default: current siteConfig (optional, default `getSiteConfig()`)
->
-> >
 
 ## For more information, read [Setup](setup/README).

docs/config/theming.md

@@ -156,10 +156,8 @@ You can create your own themes, by changing any of the given variables below. If
 
 ## Theme Variables Reference Table
 
-> **Note**\
+> **Note**
 > Variables that are unique to some diagrams can be affected by changes in Theme Variables
->
-> >
 
 | Variable             | Default/Base/Factor value      | Calc | Description                                                                                                                      |
 | -------------------- | ------------------------------ | ---- | -------------------------------------------------------------------------------------------------------------------------------- |

docs/config/usage.md

@@ -119,11 +119,9 @@ Values:
 - **antiscript**: html tags in text are allowed, (only script element is removed), click functionality is enabled
 - **sandbox**: With this security level all rendering takes place in a sandboxed iframe. This prevent any JavaScript running in the context. This may hinder interactive functionality of the diagram like scripts, popups in sequence diagram or links to other tabs/targets etc.
 
-> **Note**\
+> **Note**
 > This changes the default behaviour of mermaid so that after upgrade to 8.2, unless the `securityLevel` is not changed, tags in flowcharts are encoded as tags and clicking is disabled.
 > **sandbox** security level is still in the beta version.
->
-> >
 
 **If you are taking responsibility for the diagram source security you can set the `securityLevel` to a value of your choosing . This allows clicks and tags are allowed.**
 
@@ -188,10 +186,8 @@ Or with no config object, and a jQuery selection:
 mermaid.init(undefined, $('#someId .yetAnotherClass'));
 ```
 
-> **Warning**\
+> **Warning**
 > This type of integration is deprecated. Instead the preferred way of handling more complex integration is to use the mermaidAPI instead.
->
-> >
 
 ## Usage with webpack
 
@@ -230,7 +226,7 @@ The example code below is an extract of what mermaid does when using the API. Th
 bind events to an SVG when using the API for rendering.
 
 ```javascript
-var insertSvg = function (svgCode, bindFunctions) {
+const insertSvg = function (svgCode, bindFunctions) {
   element.innerHTML = svgCode;
   if (typeof callback !== 'undefined') {
     callback(id);
@@ -238,7 +234,7 @@ var insertSvg = function (svgCode, bindFunctions) {
   bindFunctions(element);
 };
 
-var id = 'theGraph';
+const id = 'theGraph';
 
 mermaidAPI.render(id, txt, insertSvg, element);
 ```
@@ -254,7 +250,7 @@ mermaidAPI.render(id, txt, insertSvg, element);
 This is the renderer used for transforming the documentation from Markdown to html with mermaid diagrams in the html.
 
 ```javascript
-var renderer = new marked.Renderer();
+const renderer = new marked.Renderer();
 renderer.code = function (code, language) {
   if (code.match(/^sequenceDiagram/) || code.match(/^graph/)) {
     return '<pre class="mermaid">' + code + '</pre>';
@@ -305,8 +301,8 @@ mermaid.parseError = function (err, hash) {
   displayErrorInGui(err);
 };
 
-var textFieldUpdated = function () {
-  var textStr = getTextFromFormField('code');
+const textFieldUpdated = function () {
+  const textStr = getTextFromFormField('code');
 
   if (mermaid.parse(textStr)) {
     reRender(textStr);
@@ -345,10 +341,8 @@ on what kind of integration you use.
 </script>
 ```
 
-> **Note**\
+> **Note**
 > This is the preferred way of configuring mermaid.
->
-> >
 
 ### The following methods are deprecated and are kept only for backwards compatibility.
 
@@ -364,10 +358,8 @@ approach are:
 mermaid.startOnLoad = true;
 ```
 
-> **Warning**\
+> **Warning**
 > This way of setting the configuration is deprecated. Instead the preferred way is to use the initialize method. This functionality is only kept for backwards compatibility.
->
-> >
 
 ## Using the mermaid_config
 
@@ -381,10 +373,8 @@ approach are:
 mermaid_config.startOnLoad = true;
 ```
 
-> **Warning**\
+> **Warning**
 > This way of setting the configuration is deprecated. Instead the preferred way is to use the initialize method. This functionality is only kept for backwards compatibility.
->
-> >
 
 ## Using the mermaid.init call
 
@@ -397,7 +387,5 @@ To set some configuration via the mermaid object. The two parameters that are su
 mermaid_config.startOnLoad = true;
 ```
 
-> **Warning**\
+> **Warning**
 > This way of setting the configuration is deprecated. Instead the preferred way is to use the initialize method. This functionality is only kept for backwards compatibility.
->
-> >