Move Security below Quality; reword Quality README.

UnionOfRAD · Jul 14, 2016 · ad20946 · ad20946
1 parent 2780a17
commit ad20946
Show file tree

Hide file tree

Showing 4 changed files with 13 additions and 5 deletions.
diff --git a/10_security.md → 08_quality_code/01_security.md b/10_security.md → 08_quality_code/01_security.md
diff --git a/08_quality_code/01_testing.md → 08_quality_code/02_testing.md b/08_quality_code/01_testing.md → 08_quality_code/02_testing.md
diff --git a/08_quality_code/02_analysis.md → 08_quality_code/03_analysis.md b/08_quality_code/02_analysis.md → 08_quality_code/03_analysis.md
diff --git a/08_quality_code/README.md b/08_quality_code/README.md
@@ -1,12 +1,20 @@
 # Quality Code
 
-Clean, quality and well tested code are a fundamental goals of li3.
+Clean, roboust and well tested code are fundamental goals of the framework.
 
-Li3 adheres to coding, testing and documentation standards which can be found inside the
-dedicated [specs documentation repository](/docs/specs/latest:1.x). [Static analysis](analysis) 
-tools are used to detect standards violations. 
+li₃ adheres to 
+[coding](/docs/book/specs/latest:1.x/accepted/LSR-0-coding), 
+[testing](/docs/book/specs/latest:1.x/accepted/LSR-2-testing), 
+and [documentation](/docs/book/specs/latest:1.x/accepted/LSR-1-documenting)
+standards which can be found inside the 
+[specs documentation repository](/docs/book/specs/latest:1.x). 
 
-Learn more about testing in li3 in the [Unit Testing](testing) chapter.
+[Static code analysis](analysis) tools are used to detect standards violations. 
+
+Learn how to write unit, integration and functional tests in the [Testing](testing) chapter.
+
+To make you application as robost to potential security threads as possible, follow the 
+[Securing Applications](security) guide.