summaryrefslogtreecommitdiffstats
path: root/security-blueprint/part-5/0_Abstract.md
diff options
context:
space:
mode:
authorSebastien Douheret <sebastien.douheret@iot.bzh>2017-12-08 17:40:04 +0100
committerSebastien Douheret <sebastien.douheret@iot.bzh>2017-12-08 17:40:35 +0100
commitdf4bdd6e9e5669451e7f60ecdc5c9e0d25e3f726 (patch)
treeab9ab609538816b61789ace9e5ad280cd1727a83 /security-blueprint/part-5/0_Abstract.md
parent981e9b9c4a40e248733d45cfedc6a512bdf95f5e (diff)
Added templating for section-xxx tags.
Security Blueprint doc uses specific tags to display arrays (see docs/security-blueprint/README.md) Signed-off-by: Sebastien Douheret <sebastien.douheret@iot.bzh>
Diffstat (limited to 'security-blueprint/part-5/0_Abstract.md')
-rw-r--r--security-blueprint/part-5/0_Abstract.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/security-blueprint/part-5/0_Abstract.md b/security-blueprint/part-5/0_Abstract.md
index 4cbd17a..e724321 100644
--- a/security-blueprint/part-5/0_Abstract.md
+++ b/security-blueprint/part-5/0_Abstract.md
@@ -15,12 +15,12 @@ to deal with, we must:
- Manage user capabilities (_Users_ part).
- Manage application permissions and policies (_AGLFw_ part).
-<!-- note -->
+<!-- section-note -->
The tools and concepts used to meet these needs are only examples. Any other
tool that meets the need can be used.
-<!-- endnote -->
+<!-- end-section-note -->
In AGL, as in many other embedded systems, different security mechanisms settle
in the core layers to ensure isolation and data privacy. While the Mandatory