hugo

Unnamed repository; edit this file 'description' to name the repository.

git clone git://git.shimmy1996.com/hugo.git
commit cd4d8202016bd3eb5ed9144c8945edaba73c8cf4
parent 2b28e5a9cb79af2a8d70c80036f52bcf5399b9df
Author: Onur Yaman <onuryaman@gmail.com>
Date:   Sat, 18 Apr 2020 13:57:00 +0300

docs: Fix typo in Hugo's Security Model

Diffstat:
Mdocs/content/en/about/security-model/index.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/content/en/about/security-model/index.md b/docs/content/en/about/security-model/index.md
@@ -26,7 +26,7 @@ But when developing and building your site, the runtime is the `hugo` executable
 * Hugo has a virtual file system and only the main project (not third-party components) is allowed to mount directories or files outside the project root.
 * Only the main project can walk symbolic links.
 * User-defined components have only read-access to the filesystem.
-* We shell out to some external binaries to support [Asciidoctor](/content-management/formats/#list-of-content-formats) and simliar, but those binaries and their flags are predefined. General functions to run arbitrary external OS commands have been [discussed](https://github.com/gohugoio/hugo/issues/796), but not implemented because of security concerns.
+* We shell out to some external binaries to support [Asciidoctor](/content-management/formats/#list-of-content-formats) and similar, but those binaries and their flags are predefined. General functions to run arbitrary external OS commands have been [discussed](https://github.com/gohugoio/hugo/issues/796), but not implemented because of security concerns.
 
 Hugo will soon introduce a concept of _Content Source Plugins_ (AKA _Pages from Data_), but the above will still hold true.