(opendal) 01/01: docs: fix threat model style

[er...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

erickguan pushed a commit to branch erickguan-patch-1
in repository https://gitbox.apache.org/repos/asf/opendal.git

commit 55e44c6d62f534f6ac25637c0efeb882e508c7f2
Author: Erick Guan <29...@users.noreply.github.com>
AuthorDate: Wed Jun 17 07:48:56 2026 +0800

    docs: fix threat model style
---
 SECURITY-THREAT-MODEL.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/SECURITY-THREAT-MODEL.md b/SECURITY-THREAT-MODEL.md
index ae3fce65f..e6db06a6b 100644
--- a/SECURITY-THREAT-MODEL.md
+++ b/SECURITY-THREAT-MODEL.md
@@ -49,7 +49,6 @@ hardening requests, user misuse, or out-of-scope deployment issues?
 
 The most important premises are:
 
-```suggestion
 > OpenDAL trusts storage services for fulfilling storage capabilities defined per documentation.
 > OpenDAL also trusts users to provide secure configuration and use OpenDAL as users' storage layer.
 
@@ -79,10 +78,13 @@ OpenDAL doesn't use principal model. A `Operator` takes control of a backend ser
 `Operator` instance shares the same OpenDAL-level authority.
 A typical interaction will be:
 
+```
 Trusted service <-> Backend <-> Operator <-> Host Application <-> End user
                  |                        |
                  |------------------------|
                     OpenDAL code surface
+```
+
 ## 4. Security Boundary
 
 OpenDAL's security boundary is the public library boundary plus the internal