Proofread the tutorial

I went through all the content and made the following changes:
- fixed typos
- reported some issues that were not that easy to fix (for instance the
  use of dead punkapi.com in some sections)
- adjusted the first tutorials to use Jackson instead of JSON-B: we
  recommend using Jackson. Also it avoids having to go back to switch
  from JSON-B to Jackson when dealing with Spring
- the reactive sections are still using JSON-B for two reasons: they are
  using some JSON-P features and I couldn't test things given the API is
  not available. When reworking them, we should switch them to Jackson
  too.

This is a bit massive, I will go through the changes and add comments
when they are needed.

Author: gsmet

documentation/modules/ROOT/pages/04_panache.adoc

@@ -3,7 +3,7 @@
 :project-name: tutorial-app
 
 [#quarkusp-demo-overview]
-== Demo Overview 
+== Demo Overview
 
 You'll learn how easy and productive Quarkus is with Hibernate with Panache. For this, we'll develop a simple CRUD REST API that handles information about fruits.
 
@@ -21,12 +21,12 @@ Just open a new terminal window, and make sure you're at the root of your `{proj
 [tabs]
 ====
 Maven::
-+ 
++
 --
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
-./mvnw quarkus:add-extension -Dextension="rest-jsonb, jdbc-h2, hibernate-orm-panache, smallrye-openapi"
+./mvnw quarkus:add-extension -Dextension="rest-jackson, jdbc-h2, hibernate-orm-panache, smallrye-openapi"
 ----
 
 --
@@ -36,7 +36,7 @@ Quarkus CLI::
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
-quarkus extension add rest-jsonb jdbc-h2 hibernate-orm-panache smallrye-openapi
+quarkus extension add rest-jackson jdbc-h2 hibernate-orm-panache smallrye-openapi
 ----
 --
 ====
@@ -45,7 +45,7 @@ quarkus extension add rest-jsonb jdbc-h2 hibernate-orm-panache smallrye-openapi
 [.console-output]
 [source,text]
 ----
-✅ Adding extension io.quarkus:quarkus-rest-jsonb
+✅ Adding extension io.quarkus:quarkus-rest-jackson
 ✅ Adding extension io.quarkus:quarkus-smallrye-openapi
 ✅ Adding extension io.quarkus:quarkus-hibernate-orm-panache
 ✅ Adding extension io.quarkus:quarkus-jdbc-h2
@@ -144,7 +144,7 @@ Now we should have everything in place to query our *GET* REST endpoint:
 [.console-input]
 [source,bash]
 ----
-curl localhost:8080/fruit
+curl -w '\n' localhost:8080/fruit
 ----
 
 [.console-output]
@@ -190,20 +190,19 @@ public class FruitResource {
     @Consumes(MediaType.APPLICATION_JSON)
     @Produces(MediaType.APPLICATION_JSON)
     public Response newFruit(Fruit fruit) {
-        fruit.id = null;
         fruit.persist();
         return Response.status(Status.CREATED).entity(fruit).build();
     }
 
 }
 ----
 
-Now you can insert a new fruit by using `curl`: 
+Now you can insert a new fruit by using `curl`:
 
 [.console-input]
 [source,bash]
 ----
-curl -d "{\"name\": \"Banana\", \"season\": \"Summer\"}" -H "Content-Type: application/json" http://localhost:8080/fruit
+curl -w '\n' -d "{\"name\": \"Banana\", \"season\": \"Summer\"}" -H "Content-Type: application/json" http://localhost:8080/fruit
 ----
 
 [.console-output]
@@ -237,16 +236,16 @@ Create the file `import.sql` in the folder `src/main/resources` with the followi
 [.console-input]
 [source,sql]
 ----
-create sequence fruit_sequence start with 1 increment by 1;
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Mango','Spring');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Strawberry','Spring');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Orange','Winter');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Lemon','Winter');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Blueberry','Summer');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Banana','Summer');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Watermelon','Summer');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Apple','Fall');
-INSERT INTO Fruit(id,name,season) VALUES (nextval('fruit_sequence'),'Pear','Fall');
+INSERT INTO Fruit(id,name,season) VALUES (1,'Mango','Spring');
+INSERT INTO Fruit(id,name,season) VALUES (2,'Strawberry','Spring');
+INSERT INTO Fruit(id,name,season) VALUES (3,'Orange','Winter');
+INSERT INTO Fruit(id,name,season) VALUES (4,'Lemon','Winter');
+INSERT INTO Fruit(id,name,season) VALUES (5,'Blueberry','Summer');
+INSERT INTO Fruit(id,name,season) VALUES (6,'Banana','Summer');
+INSERT INTO Fruit(id,name,season) VALUES (7,'Watermelon','Summer');
+INSERT INTO Fruit(id,name,season) VALUES (8,'Apple','Fall');
+INSERT INTO Fruit(id,name,season) VALUES (9,'Pear','Fall');
+ALTER SEQUENCE fruit_seq RESTART WITH 10;
 ----
 
 And append the following configuration in `application.properties`:
@@ -315,16 +314,16 @@ Now if you refresh your browser pointing to http://localhost:8080/fruit[window=_
 
 [TIP]
 ====
-You can add different `import.sql` files based on the application profile. 
+You can add different `import.sql` files based on the application profile.
 
-For example: in dev mode, you 
-can use the configuration `quarkus.hibernate-orm.sql-load-script=import-dev.sql`, 
+For example: in dev mode, you
+can use the configuration `quarkus.hibernate-orm.sql-load-script=import-dev.sql`,
 while in production mode you can use `quarkus.hibernate-orm.sql-load-script=import-prod.sql`.
 ====
 
 == Adding a custom finder to the `Fruit` Entity
 
-Update the `Fruit` class to contain a finder method `findBySeason` like: 
+Update the `Fruit` class to contain a finder method `findBySeason` like:
 
 [#quarkusp-find-fruits]
 [.console-input]
@@ -403,7 +402,7 @@ Let's try to filter only the fruits with the *Summer* season:
 [.console-input]
 [source,bash]
 ----
-curl localhost:8080/fruit?season=Summer
+curl -w '\n' localhost:8080/fruit?season=Summer
 ----
 
 [.console-output]
@@ -518,7 +517,7 @@ Let's try again to filter only the fruits with the *Spring* season:
 [.console-input]
 [source,bash]
 ----
-curl localhost:8080/fruit?season=Spring
+curl -w '\n' localhost:8080/fruit?season=Spring
 ----
 
 [.console-output]

documentation/modules/ROOT/pages/05_kubernetes.adoc

@@ -1,26 +1,26 @@
 =  Deploying to Kubernetes
 
 [.mt-4.right]
-image::openshift_sandbox.png[Openshift Sandbox,250,250,align="right",link="https://developers.redhat.com/developer-sandbox"]
+image::openshift_sandbox.png[OpenShift Sandbox,250,250,align="right",link="https://developers.redhat.com/developer-sandbox"]
 
-In this chapter we will push our newly built application to Kubernetes. If you don't have a Kubernetes instance at your disposal, you can create a free Openshift Sandbox instance on https://developers.redhat.com/developer-sandbox[developers.redhat.com/sandbox].
+In this chapter we will push our newly built application to Kubernetes. If you don't have a Kubernetes instance at your disposal, you can create a free OpenShift Sandbox instance on https://developers.redhat.com/developer-sandbox[developers.redhat.com/sandbox].
 
 
- 
-IMPORTANT: You will need a public container registry to store your image. If you don't have an account, we recommend to create a free account at http://quay.io[window=_blank]. 
+
+IMPORTANT: You will need a public container registry to store your image. If you don't have an account, we recommend to create a free account at http://quay.io[window=_blank].
 
 Our examples will be using the `quay.io` container registry and the `myrepo` organization, but you should change it to match your configuration.
 
 == Adding the Kubernetes and Jib extensions
 
-In this chapter we'll be using the Quarkus Kubernetes Extension to create the Kubernetes deployment file, and the Quarkus Jib Extension to create and push the container image to your container registry without the need of a local podman/docker instance.
+In this chapter we'll be using the Quarkus Kubernetes extension to create the Kubernetes deployment file, and the Quarkus Jib Extension to create and push the container image to your container registry without the need of a local Podman/Docker instance.
 
 Let's add the required extensions:
 
 [tabs]
 ====
 Maven::
-+ 
++
 --
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
@@ -67,7 +67,7 @@ quarkus.kubernetes.service-type=load-balancer<5>
 <4> Tag of the container image. By default is the `version` element of `pom.xml`.
 <5> Create an external ip for the service.
 
-IMPORTANT: Change `quay.io` to your container registry and `myrepo` to your organization. 
+IMPORTANT: Change `quay.io` to your container registry and `myrepo` to your organization.
 If you don't, your push *will* fail.
 
 == Authenticating and pushing the image to your container registry
@@ -80,12 +80,12 @@ In order to push the container image, you need to authenticate to your container
 docker login quay.io
 ----
 
-Now we're going to create the artifact, build a container and push it to our registry in one go using jib.
+Now we're going to create the artifact, build a container and push it to our registry in one go using Jib.
 
 [tabs]
 ====
 Maven::
-+ 
++
 --
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
@@ -105,7 +105,7 @@ quarkus image build jib --no-tests -D"quarkus.container-image.push=true"
 --
 ====
 
-NOTE: If you're having trouble with jib, you can also just use Docker/Podman to build & push.  To do so, omit 'jib' from the command.
+NOTE: If you're having trouble with Jib, you can also just use Docker/Podman to build and push.  To do so, omit 'jib' from the command.
 
 [.console-output]
 [source,text]
@@ -127,9 +127,9 @@ NOTE: If you're having trouble with jib, you can also just use Docker/Podman to
 
 == Deploy the application to your Kubernetes cluster
 
-When a Kubernetes extension is present in the classpath, Quarkus will scaffold a Kubernetes deployment file in your target folder during the package phase.  We can apply it to deploy the application to our Kubernetes cluster:  
+When a Kubernetes extension is present in the classpath, Quarkus will scaffold a Kubernetes deployment file in your `target/` folder during the package phase.  We can apply it to deploy the application to our Kubernetes cluster:
 
-NOTE: You will need the https://kubernetes.io/docs/tasks/tools/[kubectl] or oc cli tool installed locally for the apply command below. https://developers.redhat.com/blog/2021/04/21/access-your-developer-sandbox-for-red-hat-openshift-from-the-command-line#[Here are instructions] to install the oc tool and log in to your Openshift Sandbox.  Hint: your favorite package manager (dnf/brew/choco) can likely be used for the installation. Eg. `dnf install kubectl` or `choco install kubernetes-client` or `choco install openshift-client` 
+NOTE: You will need the https://kubernetes.io/docs/tasks/tools/[kubectl] or `oc` cli tool installed locally for the apply command below. https://developers.redhat.com/blog/2021/04/21/access-your-developer-sandbox-for-red-hat-openshift-from-the-command-line#[Here are instructions] to install the `oc` tool and log in to your OpenShift Sandbox.  Hint: your favorite package manager (dnf/brew/choco) can likely be used for the installation. Eg. `dnf install kubectl` or `choco install kubernetes-client` or `choco install openshift-client`
 
 [tabs]
 ====
@@ -161,7 +161,7 @@ deployment.apps/tutorial-app created
 ----
 
 
-With the Quarkus CLI tool deploying is even easier.  Instead of the above `kubectl apply` command, you can simply run `quarkus deploy` to deploy the application to your cluster. If you don't have the kubectl or oc cli installed or are not sure how to log in to your cluster, just add `-Dquarkus.kubernetes-client.api-server-url={yourServerUrl} -Dquarkus.kubernetes-client.token={myToken}` to the below command.
+With the Quarkus CLI tool, deploying is even easier.  Instead of the above `kubectl apply` command, you can simply run `quarkus deploy` to deploy the application to your cluster. If you don't have the `kubectl` or `oc` CLI installed or are not sure how to log in to your cluster, just add `-Dquarkus.kubernetes-client.api-server-url={yourServerUrl} -Dquarkus.kubernetes-client.token={myToken}` to the below command.
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
@@ -174,10 +174,10 @@ After the command has finished, you might need to wait a few more seconds until
 
 [tabs]
 ====
-Openshift Sandbox / Kubernetes on AWS::
+OpenShift Sandbox / Kubernetes on AWS::
 +
 --
-If using a hosted Kubernetes cluster like OpenShift (Sandbox) on AWS then use curl and the EXTERNAL-IP address with port `8080` or get it using `kubectl`:
+If using a hosted Kubernetes cluster like OpenShift (Sandbox) on AWS then use `curl` and the `EXTERNAL-IP` address with port `8080` or get it using `kubectl`:
 
 :tmp-service-exposed: tutorial-app
 
@@ -207,7 +207,7 @@ echo $IP:$PORT
 Hosted::
 +
 --
-If using a hosted Kubernetes cluster like OpenShift then use curl and the EXTERNAL-IP address with port `8080` or get it using `kubectl`:
+If using a hosted Kubernetes cluster like OpenShift then use `curl` and the `EXTERNAL-IP` address with port `8080` or get it using `kubectl`:
 
 :tmp-service-exposed: tutorial-app
 
@@ -237,18 +237,18 @@ curl $IP:$PORT/hello
 Hello y'all!
 ----
 
-If you're using the Openshift Sandbox UI, you can also find the application running in the "Topology" view as seen in the screenshot below:
+If you're using the OpenShift Sandbox UI, you can also find the application running in the "Topology" view as seen in the screenshot below:
 
 [.mt-4.center]
 image::Openshift.png[Openshift,400,400,align="center"]
 
 [sidebar]
 --
-TIP: If you're using Openshift (Sandbox) and would like to create a url you can share to the outside world, you can create it like so:
+TIP: If you're using OpenShift (Sandbox) and would like to create a url you can share to the outside world, you can create it like so:
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
-oc create route edge --service=tutorial-app 
+oc create route edge --service=tutorial-app
 url=$(oc get route tutorial-app -o jsonpath='{.spec.host}')
 curl https://$url/hello
 ----