aboutsummaryrefslogtreecommitdiffstats
path: root/src/content/docs/advanced
diff options
context:
space:
mode:
authorsaturneric <[email protected]>2025-06-23 20:51:40 +0000
committersaturneric <[email protected]>2025-06-23 20:51:40 +0000
commit21dcd3268f42ebd7d7caa4f13faa62614c105542 (patch)
treede4f1e89c21a644377c808051ded5a3c24814019 /src/content/docs/advanced
parentdocs(downloads): restructure downloads page for better clarity (diff)
downloadManual-21dcd3268f42ebd7d7caa4f13faa62614c105542.tar.gz
Manual-21dcd3268f42ebd7d7caa4f13faa62614c105542.zip
docs: fix formatting and links in documentation
- remove colon from SecureLevel 2 heading - fix link placement in getting-started guide - improve section organization in getting-started
Diffstat (limited to 'src/content/docs/advanced')
-rw-r--r--src/content/docs/advanced/memory-security.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/content/docs/advanced/memory-security.md b/src/content/docs/advanced/memory-security.md
index c03766a..5cf0571 100644
--- a/src/content/docs/advanced/memory-security.md
+++ b/src/content/docs/advanced/memory-security.md
@@ -39,7 +39,7 @@ engine (GpgME) and protected by GnuPG mechanisms. Each secure buffer is fully
initialized to zero upon allocation and is explicitly erased upon release,
minimizing the risk of residual sensitive data in memory.
-### SecureLevel 2 (Enhanced):
+### SecureLevel 2 (Enhanced)
At this highest security level, GpgFrontend utilizes OpenSSL’s secure memory
feature, allocating sensitive data into locked regions protected from being