docs: Update security-considerations.md to fix a typo (#762)

* Update 08-security-considerations.md

Add missing "t" to "untrusted"

* fix: add missing "t" to untrusted

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/versioned_docs/version-v0.20.0/08-security-considerations.md b/docs/versioned_docs/version-v0.20.0/08-security-considerations.md
index 7cab2e07..5a295526 100644
--- a/docs/versioned_docs/version-v0.20.0/08-security-considerations.md
+++ b/docs/versioned_docs/version-v0.20.0/08-security-considerations.md
@@ -2,7 +2,7 @@
 
 If you're going to give app access to untrusted users, there's some security considerations that you'll need to be aware of given how the crawler works. The crawler is basically running a browser to fetch the content of the bookmarks. Any untrusted user can submit bookmarks to be crawled from your server and they'll be able to see the crawling result. This can be abused in multiple ways:
 
-1. Untrused users can submit crawl requests to websites that you don't want to be coming out of your IPs.
+1. Untrusted users can submit crawl requests to websites that you don't want to be coming out of your IPs.
 2. Crawling user controlled websites can expose your origin IP (and location) even if your service is hosted behind cloudflare for example.
 3. The crawling requests will be coming out from your own network, which untrusted users can leverage to crawl internal non-internet exposed endpoints.