fix: fix broken link (missing scheme) and a few typos in hello world example
@@ -9,30 +9,28 @@ When the minikube is installed on your machine, you can start kubernetes using
minikube start
```
-You also probably want to configure your docker client to point the minikube docker deamon with:
+You also probably want to configure your Docker client to point the minikube Docker daemon with:
```
eval $(minikube docker-env)
```
-This will make sure that the docker images that you build are available to the minikube environment.
+This will make sure the Docker images that you build are available to the minikube environment.
# Hello World Example
This Spring Boot application exposes an endpoint that we can call to receive a `Hello World` message as response. The application is configured using the
-@RestController and the method returning the message is annotated with `@RequestMapping("/")`
+@RestController, and the method returning the message is annotated with `@RequestMapping("/")`.
-The uberjar of the Spring Boot application is packaged within a Docker image using the [Fabric8 Maven plugin](maven.fabric8.io) and next deployed top of the Kubernetes management platform as a pod
+The uberjar of the Spring Boot application is packaged within a Docker image using the [Fabric8 Maven plugin](https://maven.fabric8.io) and next deployed top of the Kubernetes management platform as a pod
using the replication controller created by the plugin.
-Once you have the environment set up (minikube or kubectl configured against a kubernetes cluster)
-
-You can play with this Spring Boot application in the cloud using the following maven command to deploy it:
+Once you have the environment set up (minikube or kubectl configured against a kubernetes cluster), you can play with this Spring Boot application in the cloud using the following maven command to deploy it:
```
mvn clean package fabric8:deploy -Pkubernetes
```
-**Note**: Unfortuntaly, when you deploy using the fabric8 plugin, the readyness and liveness probes fail to point to the right actuator URL due a lack of support for spring boot.
+**Note**: Unfortunately, when you deploy using the fabric8 plugin, the readiness and liveness probes fail to point to the right actuator URL due a lack of support for Spring Boot.
This push you to edit the generated deployment inside kubernetes and change these probes which points to "path": "/health" to "path": "/actuator/health".
This will make your deployment go green. This issue is already reported into the fabric8 community: https://github.com/fabric8io/fabric8-maven-plugin/issues/1178
