Link to GitHub repo and remove mutiny (#213)

* add solution link for github repo * remove mutiny extension as it has a transitive dependency to classic resteasy which conflicts with reactive.
acend · Nov 21, 2023 · b213156 · b213156
1 parent ebfd19b
commit b213156
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/content/en/docs/01.0/12_quarkus.md b/content/en/docs/01.0/12_quarkus.md
@@ -23,7 +23,7 @@ integration, RESTeasy-JAX-RS, dev mode and many more features.
 
 Quarkus provides a list of extensions and frameworks which can be included into
 your Quarkus project. Extensions (Hibernate ORM, Liquibase, Flyway, SmallRye
-Reactive Messageing, and many others) are minified and customized to work with
+Reactive Messaging, and many others) are minified and customized to work with
 the minimal resource consuming framework.
 
 Due to the optimization of extensions and the framework itself, Quarkus can be
@@ -74,7 +74,7 @@ be used again.
 
 In summary:
 
-* Too much classes beeing loaded
+* Too much classes being loaded
 * Too much metadata processing for annotations, cdi, reflection, proxies, ...
 
 This is where Quarkus does things differently. It moves everything possible to the build-time phase instead of run-time

diff --git a/content/en/docs/01.0/18_solutions.md b/content/en/docs/01.0/18_solutions.md
@@ -7,7 +7,7 @@ description: >
    Solution code for the Quarkus Techlabs
 ---
 
-We have provided solution code for the labs in the folder `solution` of this `quarkus-techlab` project.
+We have provided solution code for the labs in the folder `solution` of this `quarkus-techlab` project. You can find the source code of the `quarkus-techlab` on [GitHub]({{% param "github_repo" %}})
 
 {{% alert color="warning" %}}
 Be aware that in some solution projects like `quarkus-rest-data-producer` you'll find the solution code for multiple labs.

diff --git a/content/en/docs/02.0/25_reactive-programming.md b/content/en/docs/02.0/25_reactive-programming.md
@@ -382,13 +382,13 @@ curl -X POST localhost:8080/data -d "{\"data\":0.1, \"time\":\"2022-01-01T00:00:
 
 We have learned how to implement a reactive REST API to serve data in a complete reactive non-blocking way. Now it's time to take a look at the opposite, how do we reactively consume the API.
 
-Create another Quarkus project with the following extensions: `quarkus-resteasy-reactive-jackson`, `quarkus-rest-client-reactive-jackson`, `quarkus-resteasy-mutiny`:
+Create another Quarkus project with the following extensions: `quarkus-resteasy-reactive-jackson`, `quarkus-rest-client-reactive-jackson`:
 
 ```bash
 mvn io.quarkus:quarkus-maven-plugin:{{% param "quarkusVersion" %}}:create \
     -DprojectGroupId=ch.puzzle \
     -DprojectArtifactId=quarkus-reactive-rest-consumer \
-    -Dextensions="quarkus-resteasy-reactive-jackson,quarkus-rest-client-jackson,quarkus-resteasy-mutiny" \
+    -Dextensions="quarkus-resteasy-reactive-jackson,quarkus-rest-client-reactive-jackson" \
     -DprojectVersion=1.0.0 \
     -DclassName="ch.puzzle.quarkustechlab.reactiverest.consumer.boundary.DataResource"
 ```