Merge pull request eclipse#153 from xstefank/spec-fix

Fix spec text inconsistencies
xstefank · Dec 7, 2018 · b4e0d33 · b4e0d33
2 parents 6c07daa + 721c40d
commit b4e0d33
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/spec/src/main/asciidoc/java-api.adoc b/spec/src/main/asciidoc/java-api.adoc
@@ -53,7 +53,7 @@ public abstract class HealthCheckResponse {
 
 The status of all `HealthCheck` 's determines the overall status.
 
-== Constructing `HealthCheckResponse`s
+== Constructing `HealthCheckResponse` 's
 
 Application level code is expected to use one of static methods on `HealthCheckResponse` to retrieve a `HealthCheckResponseBuilder` used to construct a response, i.e. :
 

diff --git a/spec/src/main/asciidoc/overview.adoc b/spec/src/main/asciidoc/overview.adoc
@@ -37,7 +37,7 @@ all of the procedure health status.
 
 The 1.0 version of the MP-HC specification does not define how the `/health` endpoint may be partitioned in the event
 that the MicroProfile runtime supports deployment of multiple applications. If an implementation wishes to
-support multiple applications within a MicroProfile runtime, the semantics of the /health endpoint are
+support multiple applications within a MicroProfile runtime, the semantics of the `/health` endpoint are
 expected to be the logical AND of all the application in the runtime. The exact details of this are deferred to
 a future version of the MP-HC specification.
 
@@ -60,4 +60,4 @@ The proposed solution breaks down into two parts:
 - Heiko Rupp
 - Antoine Sabot-Durand
 - Scott Stark
-- Kevin Sutter
+- Kevin Sutter
diff --git a/spec/src/main/asciidoc/protocol-wireformat.adoc b/spec/src/main/asciidoc/protocol-wireformat.adoc
@@ -104,7 +104,7 @@ signal the overall status)
 
 ==== REST/HTTP interaction
 
-* Producer MUST provide a HTTP endpoint that follow the REST interface specifications described in Appendix A
+* Producer MUST provide a HTTP endpoint that follows the REST interface specifications described in Appendix A.
 
 ==== Protocol Adaptor
 
@@ -154,7 +154,7 @@ When executing health check procedures a producer MUST handle any unchecked exce
 Aspects regarding the secure access of health check information.
 
 * A producer MAY support security on all health check invocations (i.e. authentication)
-* A producer MUST not enforce security by default, it SHOULD be an opt-in feature (i.e. configuration change)
+* A producer MUST NOT enforce security by default, it SHOULD be an opt-in feature (i.e. configuration change)
 
 == Appendix A: REST interface specifications
 
@@ -343,4 +343,4 @@ Status `503` and the following payload:
   "status": "DOWN",
   "checks": []
 }
-```
+```