update documentation for "material-encryptcontent: reload all subscriptions"

Author: unverbuggt

README.md

@@ -926,20 +926,20 @@ graph LR
 
 #### mkdocs-material
 
+> **Enable by default**
+
 Add support for mermaid graphs by adding the `pymdownx.superfences` to `markdown_extensions` as 
 described [here]( https://squidfunk.github.io/mkdocs-material/reference/diagrams/).
 
-Copy the "material-encryptcontent.mjs" file from
-[here](https://github.com/unverbuggt/mkdocs-encryptcontent-plugin/tree/version3/fixes)
-to "/assets/javascripts/" and include it to "mkdocs.yml" like this:
+After successful decryption all subscriptions of the document are recalled to render the marmaid graph,
+see [here](https://github.com/unverbuggt/mkdocs-encryptcontent-plugin/pull/81).
 
-```yaml
-extra_javascript:
-  - assets/javascripts/material-encryptcontent.mjs
+```jinja
+{%- if material %}
+document$.next(document);
+{%- endif %}
 ```
 
-The script is called after successful decryption and renders the mermaid graphs in a similar way as
-the theme would normally do.
 
 ### mkdocs-glightbox
 

documentation/docs/features/jsext.md

@@ -121,20 +121,20 @@ graph LR
 
 #### mkdocs-material
 
+> **Enable by default**
+
 Add support for mermaid graphs by adding the `pymdownx.superfences` to `markdown_extensions` as 
 described [here]( https://squidfunk.github.io/mkdocs-material/reference/diagrams/).
 
-Copy the "material-encryptcontent.mjs" file from
-[here](https://github.com/unverbuggt/mkdocs-encryptcontent-plugin/tree/version3/fixes)
-to "/assets/javascripts/" and include it to "mkdocs.yml" like this:
+After successful decryption all subscriptions of the document are recalled to render the marmaid graph,
+see [here](https://github.com/unverbuggt/mkdocs-encryptcontent-plugin/pull/81).
 
-```yaml
-extra_javascript:
-  - assets/javascripts/material-encryptcontent.mjs
+```jinja
+{%- if material %}
+document$.next(document);
+{%- endif %}
 ```
 
-The script is called after successful decryption and renders the mermaid graphs in a similar way as
-the theme would normally do.
 
 ### mkdocs-glightbox
 

documentation/docs/features/security.md

@@ -128,4 +128,4 @@ all files and verify the signatures.
 As long as the private key used for signing remains secret, the canary script will be able to determine
 if someone tampered with the files on the server. But you should run the canary script from another machine
 that is not related to the server, otherwise the attacker could also modify the canary script and sign with his
-private key instead.
+private key instead.