ENDOC-606 minor changes

vuepress/docs/next/docs/getting-started/entando-cli.md

@@ -28,9 +28,8 @@ The basic requirements for the CLI vary with use case, as shown in the table bel
 
 ## Install the CLI
 Install the current official release of the CLI:
-``` bash
-curl -L https://get.entando.org/cli | bash
-```
+
+<EntandoCode> bash <(curl -L "https://get.entando.org/cli") --update --release="{{ $site.themeConfig.entando.fixpack.v71 }}" </EntandoCode>
 
 >The automatic option in [Getting Started](../getting-started/) will install the CLI along with a quickstart Entando Application.
 

vuepress/docs/next/tutorials/curate/ms-private-images.md

@@ -25,7 +25,7 @@ Supply the following parameters:
 kubectl create secret docker-registry YOUR-SECRET-NAME --docker-server=YOUR-REGISTRY-SERVER --docker-username=YOUR-USERNAME --docker-password=YOUR-PASSWORD --docker-email=YOUR-EMAIL -n entando
 ```
 
-**2b. Deploy a new Entando Application**
+**2a. Deploy a new Entando Application**
 
 If you're setting up a new Entando Application, you can [add the Secret to the Entando Operator ConfigMap](../devops/entando-operator.md) under the property `entando.k8s.operator.image.pull.secrets`. This is just a list containing the names of Docker Secrets in the operator's namespace.
 

vuepress/docs/next/tutorials/getting-started/kubernetes-install.md

@@ -32,7 +32,7 @@ The microservices tested with the CPU specs above were generated using the JHips
 Complexity, content and number of pages determine the hardware requirements of an Entando install that includes the CMS. The minimum requirements are:
 
 - 6 vCPUs for a single CMS instance. To scale up, allocate 4 vCPUs per replica.
-- 8 GB of RAM for a single CMS instance. To scale up, allocate 4 GB of RAM per replica.
+- 10 GB of RAM for a single CMS instance. To scale up, allocate 4 GB of RAM per replica.
 - A minimum of 50 GB of storage for the static resources generated by the use of the Entando CMS.
 
 ## Backup Strategies

vuepress/docs/v7.0/tutorials/curate/ecr-private-images.md

@@ -25,7 +25,7 @@ Supply the following parameters:
 kubectl create secret docker-registry YOUR-SECRET-NAME --docker-server=YOUR-REGISTRY-SERVER --docker-username=YOUR-USERNAME --docker-password=YOUR-PASSWORD --docker-email=YOUR-EMAIL -n entando
 ```
 
-**2b. Deploy a new Entando Application**
+**2a. Deploy a new Entando Application**
 
 If you're setting up a new Entando Application, you can [add the secret to the Entando Operator ConfigMap](../devops/entando-operator.md) under the property `entando.k8s.operator.image.pull.secrets`. This is just a list containing the names of Docker Secrets in the operator's namespace.
 

vuepress/docs/v7.1/docs/getting-started/entando-cli.md

@@ -28,9 +28,9 @@ The basic requirements for the CLI vary with use case, as shown in the table bel
 
 ## Install the CLI
 Install the current official release of the CLI:
-``` bash
-curl -L https://get.entando.org/cli | bash
-```
+
+<EntandoCode> bash <(curl -L "https://get.entando.org/cli") --update --release="{{ $site.themeConfig.entando.fixpack.v71 }}" </EntandoCode>
+
 
 >The automatic option in [Getting Started](../getting-started/) will install the CLI along with a quickstart Entando Application.
 

vuepress/docs/v7.1/docs/releases/README.md

@@ -19,7 +19,7 @@ Entando 7.1.0 is an important feature release that introduces major changes to t
 
 ## Breaking Changes
 * Improvements to the AppBuilder MFE framework in Entando 7.1 rely on loading MFEs as [JavaScript modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules#other_differences_between_modules_and_standard_scripts). Older widget configuration MFEs may need to be upgraded to avoid the use of SPA-style runtime files which will prevent this from working. 
-  * The latest [Create React App](https://create-react-app.dev/) defaults to this mode, so upgrading (e.g. `npx install react-scripts@latest`) may be all that is required.
+  * The latest [Create React App](https://create-react-app.dev/) defaults to this mode, so upgrading (e.g. `npm install react-scripts@latest`) may be all that is required.
   * Older React apps can be rewired via webpack config overrides using a tool such as [react-app-wired](https://github.com/timarney/react-app-rewired)
   * This console error can indicate the lack of module support in an MFE: `Uncaught TypeError: Cannot read properties of undefined (reading 'webpackJsonpreactchart')`
 * [New bundle project structure](../curate/bundle-comparison.md) supported by the [ent bundle CLI](../getting-started/ent-bundle.md) module, with self-contained directories for components and services

vuepress/docs/v7.1/tutorials/curate/ms-private-images.md

@@ -25,7 +25,7 @@ Supply the following parameters:
 kubectl create secret docker-registry YOUR-SECRET-NAME --docker-server=YOUR-REGISTRY-SERVER --docker-username=YOUR-USERNAME --docker-password=YOUR-PASSWORD --docker-email=YOUR-EMAIL -n entando
 ```
 
-**2b. Deploy a new Entando Application**
+**2a. Deploy a new Entando Application**
 
 If you're setting up a new Entando Application, you can [add the Secret to the Entando Operator ConfigMap](../devops/entando-operator.md) under the property `entando.k8s.operator.image.pull.secrets`. This is just a list containing the names of Docker Secrets in the operator's namespace.
 

vuepress/docs/v7.1/tutorials/getting-started/kubernetes-install.md

@@ -33,7 +33,7 @@ The microservices tested with the CPU specs above were generated using the JHips
 Complexity, content and number of pages determine the hardware requirements of an Entando install that includes the CMS. The minimum requirements are:
 
 - 6 vCPUs for a single CMS instance. To scale up, allocate 4 vCPUs per replica.
-- 8 GB of RAM for a single CMS instance. To scale up, allocate 4 GB of RAM per replica.
+- 10 GB of RAM for a single CMS instance. To scale up, allocate 4 GB of RAM per replica.
 - A minimum of 50 GB of storage for the static resources generated by the use of the Entando CMS.
 
 ## Backup Strategies