Merge pull request #111 from opendevstack/EDPC-1676_nongxp_option_for…

…_11_1

EDPC-1676 non-GxP template adjustments for 11.1

CHANGELOG.md

@@ -2,7 +2,7 @@
 
 ## Unreleased
 - Use a consistent notion of document version ([#95](https://github.com/opendevstack/ods-document-generation-templates/issues/95))
-- CFTP Templates adjusted to support non-GxP projects ([#100](https://github.com/opendevstack/ods-document-generation-templates/issues/100))
+- CFTP templates adjusted to support non-GxP projects ([#100](https://github.com/opendevstack/ods-document-generation-templates/issues/100))
 - Improve Document Generation Experience ([#97](https://github.com/opendevstack/ods-document-generation-templates/issues/97))
 - Update Reference Documents & Base Documents sections ([#101](https://github.com/opendevstack/ods-document-generation-templates/issues/101))
 - Fix SSDS appendix per gamp and RA chapter 5 ([#103](https://github.com/opendevstack/ods-document-generation-templates/issues/103))

templates/CFTP-4.html.tmpl

@@ -317,7 +317,7 @@
             All discrepancies occurring during the test execution are automatically recorded in a designated discrepancy log.
             {{#if metadata.gxp}}
                 In case of a re-deployment, a rationale must be documented in a manually created C-DIL document. When advancing to the P environment despite failed test cases or exclusions from testing, a rationale including the analyzed risks must be documented in a manually created C-FTR document (Appendix 1).
-            {{/}}
+            {{/if}}
         </p>
         <h3 id="section_11_2"><span>11.2</span> Manual Test Cases</h3>
         <p>Upon failing a test case, the Tester shall always contact the Test Administrator immediately to review the problem. The Test Administrator shall decide how to proceed, since test cases may build upon each other and a failure may cascade through several cases.</p>