From e3d1f8eb20d4dbdd082da517a5b3db65d8038cf6 Mon Sep 17 00:00:00 2001 From: Andrew Jandacek <38347291+janan07@users.noreply.github.com> Date: Mon, 3 Aug 2020 15:14:45 +0200 Subject: [PATCH] Refactor lines 161, 348, and 364 (#91) Signed-off-by: Andrew Jandacek --- zowe_conformance/test_evaluation_guide_table.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/zowe_conformance/test_evaluation_guide_table.md b/zowe_conformance/test_evaluation_guide_table.md index 83fbd2c..6bf5794 100644 --- a/zowe_conformance/test_evaluation_guide_table.md +++ b/zowe_conformance/test_evaluation_guide_table.md @@ -158,7 +158,7 @@ These Zowe Conformance criteria are applicable to the lastest Zowe v1 LTS Releas x -  - ui/v1/{serviceId} reserved for UIs +  - ws/v1/{serviceId} reserved for WebSockets @@ -345,7 +345,7 @@ These Zowe Conformance criteria are applicable to the lastest Zowe v1 LTS Releas x - API - in JSON format, relative links, and must not contain schema, hostname, and port + API - in JSON format, use relative links, and must not contain schema, hostname, and port. Alternatively, an absolute link can be used, in which case the service must translate the link to the form that goes through the Gateway that is based on the X-Forwarded-* Headers 21 @@ -361,7 +361,7 @@ These Zowe Conformance criteria are applicable to the lastest Zowe v1 LTS Releas x - UI - The UI uses relative links and does not contain the schema, hostname, and port + UI - The UI uses relative links and does not contain the schema, hostname, and port. Alternatively an absolute link can be used, in which case the service must translate the link to the form that goes through the Gateway that is based on the X-Forwarded-* Headers