Merge remote-tracking branch 'upstream/master'

Author: krishi-agrawal

content/documentation/guides/administration/snapshots.md

@@ -21,7 +21,7 @@ Microcks Snapshots are not complete database exports because they only integrate
 
 > 🚨 **Warning**
 >
-> Snapshots cannot be substitutes for proper database backup and restore procedures! If you choose to deploy Microcks as a central instance that should always up-and-runing, databases backups are necessary to keep all the history of different objects and retain the configuration of your instance.
+> Snapshots cannot be substitutes for proper database backup and restore procedures! If you choose to deploy Microcks as a central instance that should always up-and-running, databases backups are necessary to keep all the history of different objects and retain the configuration of your instance.
 
 Snapshots are lightweight structures that can be used to:
 * easily exchange a set of Services & APIs definition with another instance of Microcks,

content/documentation/guides/installation/kubernetes-operator.md

@@ -194,7 +194,7 @@ kubectl patch -n ingress-nginx deployment/ingress-nginx-controller --type='json'
     -p '[{"op":"add","path":"/spec/template/spec/containers/0/args/-","value":"--enable-ssl-passthrough"}]'
 ```
 
-So assuming you're having the Strimzi operator up and runing in your `microcks` namespace, you can now create a new Microcks instance with additional properties to enable the asynchronous feature and to popup a new Kafka cluster that will be made available to users at `kafka.m.minikube.local`:
+So assuming you're having the Strimzi operator up and runinng in your `microcks` namespace, you can now create a new Microcks instance with additional properties to enable the asynchronous feature and to popup a new Kafka cluster that will be made available to users at `kafka.m.minikube.local`:
 
 ```yaml
 cat <<EOF | kubectl apply -n microcks -f -

content/documentation/tutorials/first-asyncapi-mock.md

@@ -21,7 +21,7 @@ Ready? Go! 💥
 
 First mandatory step is obviously to setup Microcks 😉. For AsyncAPI usage, we need a particular setup that embeds an Apache Kafka broker linked to a Microcks instance. Do not worry, we made this available for you as a simple `docker compose` command! 
 
-> As an alternative, you could also use our [Docker Desktop Extension](https://microcks.io/documentation/guides/installation/docker-desktop-extension/) is you feel more comfortable with graphical tools.
+> As an alternative, you could also use our [Docker Desktop Extension](https://microcks.io/documentation/guides/installation/docker-desktop-extension/) if you feel more comfortable with graphical tools.
 
 To retrieve and start the `docker compose` configuration, just execute the following commands, adapting the folder to one of your choice:
 

content/documentation/tutorials/getting-started-tests.md

@@ -52,7 +52,7 @@ Now you have everything ready to launch your first test with Microcks!
 Now that our component implementing the API is running, it's time to launch some tests to check if it is actually compliant with the API Contract. This is what we call **Contract Testing**. You can launch and run tests from the UI or from the [`microcks-cli`](/documentation/guides/automation/cli/) tool.
 
 > 💡 
-> As our API implement is runing into a container bound on port 8282, it will be accessible at `http://localhost:8282` from our machine network. However, from the Microcks container perspective it will be accessible using the `http://host.docker.internal:8282` alias that allow accessing the machine network from inside a container.
+> As our API implement is running into a container bound on port 8282, it will be accessible at `http://localhost:8282` from our machine network. However, from the Microcks container perspective it will be accessible using the `http://host.docker.internal:8282` alias that allow accessing the machine network from inside a container.
 
 
 ### From the UI

public

@@ -25,6 +25,30 @@ entries:
     urls:
     - https://microcks.io/helm/microcks-1.11.0.tgz
     version: 1.11.0
+  - apiVersion: v2
+    appVersion: 1.11.0
+    created: "2025-02-10T10:56:22.018108+01:00"
+    description: Microcks - API Mocking and Testing
+    digest: 6aa214c76ffc5f0021acdc9bffb6b9a603151b80625e2e3ac0564d6c8a394d8a
+    home: https://microcks.io
+    icon: https://microcks.io/images/microcks-big.png
+    keywords:
+    - mocks
+    - microservice
+    - api
+    - test
+    kubeVersion: '>=1.17.0-0'
+    maintainers:
+    - email: laurent.broudoux@gmail.com
+      name: Laurent Broudoux
+    name: microcks
+    sources:
+    - http://github.com/microcks/microcks/
+    - https://microcks.io
+    type: application
+    urls:
+    - https://microcks.io/helm/microcks-1.11.0-fix-2.tgz
+    version: 1.11.0-fix-2
   - apiVersion: v2
     appVersion: 1.10.1
     created: "2024-09-30T10:38:51.344773+02:00"
@@ -601,4 +625,4 @@ entries:
     urls:
     - https://microcks.io/helm/microcks-0.8.0.tgz
     version: 0.8.0-helm-3.kube-1.17
-generated: "2025-01-15T14:34:10.795802+01:00"
+generated: "2025-02-10T10:56:22.01652+01:00"