Revising tagging conformance criteria for correctness (#130)

Signed-off-by: 1000TurquoisePogs <[email protected]>
openmainframeproject · Sep 29, 2020 · 98c6098 · 98c6098
1 parent ae2a773
commit 98c6098
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/zowe_conformance/test_evaluation_guide.md b/zowe_conformance/test_evaluation_guide.md
@@ -233,7 +233,7 @@ These Zowe Conformant criteria are applicable to the lastest Zowe v1 LTS Release
 
 10. **Encoding**
 
-    a. To enable an App to work with z/OS Node.js version 12 or higher, all application files must be tagged according to their content type. **(required)**
+    a. Application Framework plugins serving web content through App Server or doing file I/O through an App Server dataservice should tag these files on z/OS according to their content type. **(best practice)**
 
     b. Testing Apps via the install-app script is advisable to enable end users to utilize Zowe plugin management tooling. **(best practice)**
 

diff --git a/zowe_conformance/test_evaluation_guide_table.md b/zowe_conformance/test_evaluation_guide_table.md
@@ -1087,10 +1087,10 @@ These Zowe Conformance criteria are applicable to the lastest Zowe v1 LTS Releas
  <tr>
    <th style="background-color:#555555">25</th>
    <th style="background-color:#555555">v1</th>
-   <th style="background-color:#AAAAAA">x</th>
    <th style="background-color:#AAAAAA"></th>
+   <th style="background-color:#AAAAAA">x</th>
    <th></th>
-   <td>To enable an App to work with z/OS Node.js version 12 or higher, all application files must be tagged according to their content type</td>
+   <td>Application Framework plugins serving web content through App Server or doing file I/O through an App Server dataservice should tag these files on z/OS according to their content type</td>
  </tr>
  <tr>
    <th style="background-color:#555555">26</th>