diff options
| author | Mo-Gul <Mo-Gul@gmx.net> | 2022-08-16 07:51:09 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-15 23:51:09 -0600 |
| commit | 81e3e772f1294f85a5be7d34d06e132494c44e5b (patch) | |
| tree | d4a589b9cc517a56298fe0192573fb77b6835239 | |
| parent | 63ed24ad0b7c03b2e24133a607c5c1a057fb8569 (diff) | |
doc: fix typo (PR #4332)
| -rw-r--r-- | docs/modules/ROOT/pages/safe-modes.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/modules/ROOT/pages/safe-modes.adoc b/docs/modules/ROOT/pages/safe-modes.adoc index 27e94462..395ac728 100644 --- a/docs/modules/ROOT/pages/safe-modes.adoc +++ b/docs/modules/ROOT/pages/safe-modes.adoc @@ -9,7 +9,7 @@ Each level includes the restrictions enabled in the prior security level. Asciidoctor's safe modes are primarily focused on what the processor is permitted to do. The safe modes do not provide a comprehensive security framework. In particular, there's no safe mode that restricts the kind of content the author can pass through to the output document. -In other words, the safe mode setting does not provide a way to santiize the output. +In other words, the safe mode setting does not provide a way to sanitize the output. Asciidoctor performs sensible escaping to allow an author to safely input text, but does not limit the content that can be included in the output using passthrough blocks or custom substitutions. The reason for this policy is that we assume the document will be passed through a sanitizer if the HTML must be embedded directly into a web page, precisely what GitHub and GitLab do. |