Replaced HealthCheck by Health Check

fabric8-launcher · Nov 3, 2017 · db27e3e · db27e3e
1 parent c34e069
commit db27e3e
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/topics/nodejs-runtime-overview.adoc b/docs/topics/nodejs-runtime-overview.adoc
@@ -4,4 +4,4 @@
 
 {NodeJS} is a JavaScript runtime built on link:https://developers.google.com/v8/[Chrome's V8 JavaScript engine]. {NodeJS} uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. {NodeJS}' package ecosystem, link:https://www.npmjs.com/[npm], is the largest ecosystem of open source libraries in the world.
 
-The {NodeJS} runtime enables you to run {NodeJS} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, continuous delivery pipelines, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover.
+The {NodeJS} runtime enables you to run {NodeJS} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, continuous delivery pipelines, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.
diff --git a/docs/topics/sb-tomcat-runtime-overview.adoc b/docs/topics/sb-tomcat-runtime-overview.adoc
@@ -2,4 +2,4 @@
 //https://projects.spring.io/spring-boot/ 
 {SpringBoot} enables you to create opinionated Spring-based standalone applications. Check out xref:sb-tomcat-additional-resources[Additional Resources] for further reading on {SpringBoot}.
 
-The {SpringBoot} runtime enables you to run {SpringBoot} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover. 
+The {SpringBoot} runtime enables you to run {SpringBoot} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.
diff --git a/docs/topics/vertx-runtime-overview.adoc b/docs/topics/vertx-runtime-overview.adoc
@@ -4,4 +4,4 @@
 
 {VertX} is a toolkit for writing reactive, non-blocking, asynchronous applications that run on the JVM. {VertX} provides an unopinionated and flexible way to write polyglot applications that are fast and lightweight. {VertX} is also designed to be truly cloud-native by efficiently allowing many processes to switch between one or very few threads. This allows {VertX} applications and services to more effectively use their CPU quotas in cloud environments and avoids the unnecessary overhead caused when creating new threads. Check out xref:vertx-additional-resources[Additional Resources] for further reading on {VertX}.
 
-Using the {VertX} runtime in OpenShift makes it simpler and easier to build reactive systems with {VertX}. The {VertX} runtime enables you to run {VertX} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover. 
+Using the {VertX} runtime in OpenShift makes it simpler and easier to build reactive systems with {VertX}. The {VertX} runtime enables you to run {VertX} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.
diff --git a/docs/topics/wf-swarm-runtime-overview.adoc b/docs/topics/wf-swarm-runtime-overview.adoc
@@ -3,4 +3,4 @@
 
 {WildFlySwarm} deconstructs the features in link:http://wildfly.org[WildFly Java Application Server] and allows them to be selectively reconstructed based on the needs of your application. This allows you to create microservices that run on a _just-enough-appserver_ that supports the exact subset of APIs you need. Check out xref:wf-swarm-additional-resources[Additional Resources] for further reading on {WildFlySwarm}.
 
-The {WildFlySwarm} runtime enables you to run {WildFlySwarm} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover. 
+The {WildFlySwarm} runtime enables you to run {WildFlySwarm} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,4 +4,4 @@

		{NodeJS} is a JavaScript runtime built on link:https://developers.google.com/v8/[Chrome's V8 JavaScript engine]. {NodeJS} uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. {NodeJS}' package ecosystem, link:https://www.npmjs.com/[npm], is the largest ecosystem of open source libraries in the world.

		The {NodeJS} runtime enables you to run {NodeJS} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, continuous delivery pipelines, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover.
		The {NodeJS} runtime enables you to run {NodeJS} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, continuous delivery pipelines, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,4 +4,4 @@

		{VertX} is a toolkit for writing reactive, non-blocking, asynchronous applications that run on the JVM. {VertX} provides an unopinionated and flexible way to write polyglot applications that are fast and lightweight. {VertX} is also designed to be truly cloud-native by efficiently allowing many processes to switch between one or very few threads. This allows {VertX} applications and services to more effectively use their CPU quotas in cloud environments and avoids the unnecessary overhead caused when creating new threads. Check out xref:vertx-additional-resources[Additional Resources] for further reading on {VertX}.

		Using the {VertX} runtime in OpenShift makes it simpler and easier to build reactive systems with {VertX}. The {VertX} runtime enables you to run {VertX} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover.
		Using the {VertX} runtime in OpenShift makes it simpler and easier to build reactive systems with {VertX}. The {VertX} runtime enables you to run {VertX} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -3,4 +3,4 @@

		{WildFlySwarm} deconstructs the features in link:http://wildfly.org[WildFly Java Application Server] and allows them to be selectively reconstructed based on the needs of your application. This allows you to create microservices that run on a _just-enough-appserver_ that supports the exact subset of APIs you need. Check out xref:wf-swarm-additional-resources[Additional Resources] for further reading on {WildFlySwarm}.

		The {WildFlySwarm} runtime enables you to run {WildFlySwarm} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, HealthCheck, Circuit Breaker, and Failover.
		The {WildFlySwarm} runtime enables you to run {WildFlySwarm} applications and services in OpenShift while providing all the advantages and conveniences of the OpenShift platform such as rolling updates, service discovery, and canary deployments. OpenShift also makes it easier for your applications to implement common microservice patterns such as ConfigMap, Health Check, Circuit Breaker, and Failover.