diff --git a/spec/src/main/asciidoc/overview.adoc b/spec/src/main/asciidoc/overview.adoc
index 923be83..60a5e91 100644
--- a/spec/src/main/asciidoc/overview.adoc
+++ b/spec/src/main/asciidoc/overview.adoc
@@ -39,7 +39,7 @@ subcomponent of an application.
 In an application, there can be zero or more procedures bound to a given health endpoint.
 The overall application health for a given endpoint is the logical AND of all of the procedures bound to it.
 
-The current version of the MP-HC specification does not define how the `/health/live` and `/health/ready` endpoints may be partitioned in the event
+The current version of the MP-HC specification does not define how the defined endpoints 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 individual endpoints are
 expected to be the logical AND of all the application in the runtime. The exact details of this are deferred to
diff --git a/spec/src/main/asciidoc/protocol-wireformat.adoc b/spec/src/main/asciidoc/protocol-wireformat.adoc
index d7a76f2..ef1ae0a 100644
--- a/spec/src/main/asciidoc/protocol-wireformat.adoc
+++ b/spec/src/main/asciidoc/protocol-wireformat.adoc
@@ -191,7 +191,7 @@ Aspects regarding the secure access of health check information.
 
 === Response Codes and status mappings
 
-The following table give valid health check responses for all kind of health checks:
+The following table gives valid health check responses for all kinds of health checks:
 
 |===
 | Request | HTTP Status       | JSON Payload         | State  | Comment