docs: updating minikube and crc installation guides (eclipse-che#2302)

Co-authored-by: Kevin Owen <[email protected]>
Co-authored-by: Fabrice Flore-Thébault <[email protected]>

modules/administration-guide/pages/installing-che-on-minikube.adoc

@@ -18,6 +18,4 @@ include::partial$proc_using-minikube-to-set-up-kubernetes.adoc[leveloffset=+1]
 
 include::partial$proc_installing-che-on-minikube-using-chectl.adoc[leveloffset=+1]
 
-include::partial$proc_using-minikube-and-lxc.adoc[leveloffset=+1]
-
 :context: {parent-context-of-installing-che-on-minikube}

modules/administration-guide/partials/proc_using-chectl-to-install-che-on-codeready-containers.adoc

@@ -5,51 +5,39 @@
 [id="using-{prod-cli}-to-install-{prod-id-short}-on-codeready-containers_{context}"]
 = Using {prod-cli} to install {prod-short} on CodeReady Containers 
 
-This section describes how to install {prod-short} on CodeReady Containers (CRC) using `{prod-cli}`.
+This section describes how to install {prod-short} on CodeReady Containers using `{prod-cli}`.
 
 .Prerequisites
 
 * The `{prod-cli}` management tool is available. See xref:using-the-chectl-management-tool.adoc[].
 * An installation of CodeReady Containers. See link:https://console.redhat.com/openshift/create/local[Installing CodeReady Containers].
-* The path to the user's CRC pull secret is known.
+* The path to the user's CodeReady Containers pull secret is known as __<pull-secret-file>__.
 
 .Procedure
 
-. Initiate the CRC platform:
-
-.. Configure your host machine for CodeReady Containers:
-+
-----
-$ crc setup
-----
-
-.. Remove any previous cluster:
+. Remove any previous cluster:
 +
 ----
 $ crc delete
 ----
 
-.. Initiate the `oc` command line interface within CRC: 
+. Configure your host machine for CodeReady Containers:
 +
 ----
-$ eval $(crc oc-env)
+$ crc setup
 ----
 
-.. Start the CodeReady Containers virtual machine with at least 12 GB of RAM and specify the path to your pull secret:
+. Start the CodeReady Containers virtual machine with at least 12 GB of RAM and specify the path to your pull secret, and take note of the password for the user `kubeadmin`, displayed at the end of the CodeReady Containers initiation:
 +
 [subs="+quotes"]
 ----
-$ crc start --memory 12288 --pull-secret-file __<download-path>__pull-secret.txt
+$ crc start --memory 12288 --pull-secret-file __<pull-secret-file>__
 ----
 
-.. Take note of the password for the user `kubeadmin`, displayed at the end of the CRC initiation.
-
-. Log into the OpenShift cluster using the `kubeadmin` username, the corresponding `__<kubeadmin-password>__` password, and the CRC URL pointer displayed at the end of the CRC initiation phase:
+. Enable access to the `oc` command line interface embedded in CodeReady Containers:
 +
-[subs="+quotes"]
 ----
-$ oc login --username="kubeadmin" --password="__<kubeadmin-password>__" https://api.crc.testing:6443
-
+$ eval $(crc oc-env)
 ----
 
 . Install the {prod-short} instance using {prod-cli}:
@@ -59,15 +47,6 @@ $ oc login --username="kubeadmin" --password="__<kubeadmin-password>__" https://
 $ {prod-cli} server:deploy --platform crc
 ----
 
-. Use the Users Dashboard CRC testing URL and sign in as:
-+
-----
-Login: developer
-Password: developer
-----
-
-. Enter the user's credentials and start using {prod-short}.
-
 
 .Additional resources
 

modules/administration-guide/partials/proc_using-minikube-to-set-up-kubernetes.adoc

@@ -14,8 +14,8 @@ This section describes how to use Minikube to prepare a local single-node {kuber
 
 .Procedure
 
-. Start Minikube (it is important to *allocate at least 4GB of RAM but 8GB are recommended*):
+. Start Minikube. Allocate at least 8GB of RAM and 4 CPU cores:
 +
 ----
-$ minikube start --addons=ingress --vm=true --memory=8192
+$ minikube start --addons=ingress --vm=true --memory=8192 --cpus=4
 ----