Merge pull request #613 from entando/ENDOC-598

ENDOC-598 linkchecker edits
entando · Oct 31, 2022 · 384efaf · 384efaf
2 parents 1074346 + 4f85982
commit 384efaf
Show file tree

Hide file tree

Showing 6 changed files with 7 additions and 7 deletions.
diff --git a/vuepress/docs/next/docs/curate/how-microservices-connect-to-apps.md b/vuepress/docs/next/docs/curate/how-microservices-connect-to-apps.md
@@ -11,7 +11,7 @@ In order to fully understand the concepts explained in this piece of the documen
 
 When a bundle containing a microservice is installed using the ECR, behind the scenes some actions take place.
 
-1. To begin, an [EntandoPlugin custom resource](https://github.com/entando-k8s/entando-k8s-custom-model/blob/master/src/main/resources/crd/EntandoPluginCRD.yaml) is generated starting from the PluginDescriptor. Some fields will be automatically generated from the provided image.
+1. To begin, an [EntandoPlugin custom resource](https://github.com/entando-k8s/entando-k8s-custom-model/blob/master/src/main/resources/crd/entandoplugins.entando.org.crd.yaml) is generated starting from the PluginDescriptor. Some fields will be automatically generated from the provided image.
 - From the `image` field in the PluginDescriptor, we will extract the `organization`, `name` and `version` of the image.
 - `organization`, `name` and `version` are then converted to valid characters and composed to form the plugin name (`metadata.name`), the labels (`metadata.labels`) and the ingressPath (`spec.ingressPath`) of the custom resource.
 

diff --git a/vuepress/docs/next/tutorials/create/ms/update-data-model.md b/vuepress/docs/next/tutorials/create/ms/update-data-model.md
@@ -24,7 +24,7 @@ entity Conference {
   name String
 }
 ```
-3. Enhance this definition by adding fields, entities, table mappings, field validation, etc. This is easily accomplished with the [online JDL-Studio or corresponding JHipster IDE plugins/extensions](https://www.jhipster.tech/jdl/). For example:
+3. Enhance this definition by adding fields, entities, table mappings, field validation, etc. This is easily accomplished with the [online JDL-Studio or corresponding JHipster IDE plugins/extensions](https://www.jhipster.tech/jdl/intro). For example:
 ```
 entity Conference {
   name String required

diff --git a/vuepress/docs/next/tutorials/curate/ms-private-images.md b/vuepress/docs/next/tutorials/curate/ms-private-images.md
@@ -14,10 +14,10 @@ The standard deployment of Entando assumes that microservice images are pulled f
 ## Tutorial
 The first step demonstrates how to create a Secret for Docker Hub. See the [corresponding Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry) for other options.
 
-**1. Create the secret**
+**1. Create the secret** 
 Supply the following parameters:
 * The name of the new Secret, e.g. `my-docker-secret`
-* The URL to your registry server. For Docker Hub, this is currently <https://index.docker.io/v1/>
+* The URL to your registry server. For Docker Hub, this is currently `https://registry.hub.docker.com/`.
 * Your Docker Hub username, password, and email.
 * The Entando namespace, e.g. `entando` for a quickstart environment
 

diff --git a/vuepress/docs/v7.1/docs/curate/how-microservices-connect-to-apps.md b/vuepress/docs/v7.1/docs/curate/how-microservices-connect-to-apps.md
@@ -11,7 +11,7 @@ In order to fully understand the concepts explained in this piece of the documen
 
 When a bundle containing a microservice is installed using the ECR, behind the scenes some actions take place.
 
-1. To begin, an [EntandoPlugin custom resource](https://github.com/entando-k8s/entando-k8s-custom-model/blob/master/src/main/resources/crd/EntandoPluginCRD.yaml) is generated starting from the PluginDescriptor. Some fields will be automatically generated from the provided image.
+1. To begin, an [EntandoPlugin custom resource](https://github.com/entando-k8s/entando-k8s-custom-model/blob/master/src/main/resources/crd/entandoplugins.entando.org.crd.yaml) is generated starting from the PluginDescriptor. Some fields will be automatically generated from the provided image.
 - From the `image` field in the PluginDescriptor, we will extract the `organization`, `name` and `version` of the image.
 - `organization`, `name` and `version` are then converted to valid characters and composed to form the plugin name (`metadata.name`), the labels (`metadata.labels`) and the ingressPath (`spec.ingressPath`) of the custom resource.
 

diff --git a/vuepress/docs/v7.1/tutorials/create/ms/update-data-model.md b/vuepress/docs/v7.1/tutorials/create/ms/update-data-model.md
@@ -24,7 +24,7 @@ entity Conference {
   name String
 }
 ```
-3. Enhance this definition by adding fields, entities, table mappings, field validation, etc. This is easily accomplished with the [online JDL-Studio or corresponding JHipster IDE plugins/extensions](https://www.jhipster.tech/jdl/). For example:
+3. Enhance this definition by adding fields, entities, table mappings, field validation, etc. This is easily accomplished with the [online JDL-Studio or corresponding JHipster IDE plugins/extensions](https://www.jhipster.tech/jdl/intro). For example:
 ```
 entity Conference {
   name String required

diff --git a/vuepress/docs/v7.1/tutorials/curate/ms-private-images.md b/vuepress/docs/v7.1/tutorials/curate/ms-private-images.md
@@ -17,7 +17,7 @@ The first step demonstrates how to create a Secret for Docker Hub. See the [corr
 **1. Create the secret**
 Supply the following parameters:
 * The name of the new Secret, e.g. `my-docker-secret`
-* The URL to your registry server. For Docker Hub, this is currently <https://index.docker.io/v1/>
+* The URL to your registry server. For Docker Hub, this is currently `https://registry.hub.docker.com/`.
 * Your Docker Hub username, password, and email.
 * The Entando namespace, e.g. `entando` for a quickstart environment