docs: remove ids

Signed-off-by: Fabrice Flore-Thébault <ffloreth@redhat.com>
crc-org · Jun 29, 2023 · a574a0b · a574a0b
1 parent 0a10e39
commit a574a0b
Show file tree

Hide file tree

Showing 33 changed files with 0 additions and 37 deletions.
diff --git a/.../modules/getting_started/partials/assembly_accessing-the-openshift-cluster.adoc b/.../modules/getting_started/partials/assembly_accessing-the-openshift-cluster.adoc
@@ -1,4 +1,3 @@
-[id="accessing-the-openshift-cluster_{context}"]
 = Accessing the {openshift} cluster
 
 Access the {ocp} cluster running in the {prod} instance by using the {ocp} web console or {openshift} CLI ([command]`oc`).

diff --git a/docs/modules/getting_started/partials/con_about-configuration.adoc b/docs/modules/getting_started/partials/con_about-configuration.adoc
@@ -1,4 +1,3 @@
-[id="about-configuration_{context}"]
 = About {prod} configuration
 
 Use the [command]`{bin} config` command to configure both the [command]`{bin}` executable and the {prod} instance.

diff --git a/docs/modules/getting_started/partials/con_about-presets.adoc b/docs/modules/getting_started/partials/con_about-presets.adoc
@@ -1,4 +1,3 @@
-[id="about-presets_{example$snip_{project-context}}"]
 = About presets
 
 [role="_abstract"]

diff --git a/docs/modules/getting_started/partials/con_about-usage-data-collection.adoc b/docs/modules/getting_started/partials/con_about-usage-data-collection.adoc
@@ -1,4 +1,3 @@
-[id="about-usage-data-collection_{example$snip_{project-context}}"]
 = About usage data collection
 
 {prod} prompts you before use for optional, anonymous usage data collection to assist with development.

diff --git a/docs/modules/getting_started/partials/con_about.adoc b/docs/modules/getting_started/partials/con_about.adoc
@@ -1,4 +1,3 @@
-[id="about_{context}"]
 = About {prod}
 
 {rh-prod} brings a minimal {ocp} 4 cluster and Podman container runtime to your local computer.

diff --git a/...getting_started/partials/con_differences-from-production-openshift-install.adoc b/...getting_started/partials/con_differences-from-production-openshift-install.adoc
@@ -1,4 +1,3 @@
-[id="differences-from-production-openshift-install_{context}"]
 = Differences from a production {ocp} installation
 
 The {openshift} preset for {rh-prod} provides a regular {ocp} installation with the following notable differences:

diff --git a/...es/getting_started/partials/proc_accessing-the-internal-openshift-registry.adoc b/...es/getting_started/partials/proc_accessing-the-internal-openshift-registry.adoc
@@ -1,4 +1,3 @@
-[id="accessing-the-internal-openshift-registry_{context}"]
 = Accessing the internal {openshift} registry
 
 The {ocp} cluster running in the {prod} instance includes an internal container image registry by default.

diff --git a/...ules/getting_started/partials/proc_accessing-the-openshift-cluster-with-oc.adoc b/...ules/getting_started/partials/proc_accessing-the-openshift-cluster-with-oc.adoc
@@ -1,4 +1,3 @@
-[id="accessing-the-openshift-cluster-with-oc_{context}"]
 = Accessing the {openshift} cluster with the {openshift} CLI
 
 Access the {ocp} cluster managed by {prod} by using the {openshift} CLI ([command]`oc`).

diff --git a/.../modules/getting_started/partials/proc_accessing-the-openshift-web-console.adoc b/.../modules/getting_started/partials/proc_accessing-the-openshift-web-console.adoc
@@ -1,4 +1,3 @@
-[id="accessing-the-openshift-web-console_{context}"]
 = Accessing the {openshift} web console
 
 Access the {ocp} web console by using your web browser.

diff --git a/docs/modules/getting_started/partials/proc_changing-the-selected-preset.adoc b/docs/modules/getting_started/partials/proc_changing-the-selected-preset.adoc
@@ -1,4 +1,3 @@
-[id="changing-the-selected-preset_{context}"]
 = Changing the selected preset
 
 [role="_abstract"]

diff --git a/docs/modules/getting_started/partials/proc_configuring-the-instance.adoc b/docs/modules/getting_started/partials/proc_configuring-the-instance.adoc
@@ -1,4 +1,3 @@
-[id="configuring-the-instance_{context}"]
 = Configuring the instance
 
 Use the `cpus` and `memory` properties to configure the default number of vCPUs and amount of memory available to the {prod} instance, respectively.

diff --git a/docs/modules/getting_started/partials/proc_configuring-usage-data-collection.adoc b/docs/modules/getting_started/partials/proc_configuring-usage-data-collection.adoc
@@ -1,4 +1,3 @@
-[id="configuring-usage-data-collection_{context}"]
 = Configuring usage data collection
 
 Consent for usage data collection can be granted or revoked by you at any time using the following configuration commands.

diff --git a/docs/modules/getting_started/partials/proc_connecting-to-remote-instance.adoc b/docs/modules/getting_started/partials/proc_connecting-to-remote-instance.adoc
@@ -1,4 +1,3 @@
-[id="connecting-to-remote-instance_{context}"]
 = Connecting to a remote {prod} instance
 
 Use [application]`dnsmasq` to connect a client machine to a remote server running an {ocp} cluster managed by {prod}.

diff --git a/docs/modules/getting_started/partials/proc_deleting-the-instance.adoc b/docs/modules/getting_started/partials/proc_deleting-the-instance.adoc
@@ -1,4 +1,3 @@
-[id="deleting-the-instance_{context}"]
 = Deleting the instance
 
 The [command]`{bin} delete` command deletes an existing {prod} instance.

diff --git a/...odules/getting_started/partials/proc_deploying-sample-application-with-odo.adoc b/...odules/getting_started/partials/proc_deploying-sample-application-with-odo.adoc
@@ -1,4 +1,3 @@
-[id="deploying-sample-application-with-odo_{context}"]
 = Deploying a sample application with `odo`
 
 You can use [command]`odo` to create {openshift} projects and applications from the command line.

diff --git a/docs/modules/getting_started/partials/proc_enabling-override-operators.adoc b/docs/modules/getting_started/partials/proc_enabling-override-operators.adoc
@@ -1,4 +1,3 @@
-[id="enabling-override-operators_{context}"]
 = Enabling override Operators
 
 To verify {prod} can run on a typical notebook, some resource-heavy services get disabled by default.

diff --git a/...etting_started/partials/proc_getting-shell-access-to-the-openshift-cluster.adoc b/...etting_started/partials/proc_getting-shell-access-to-the-openshift-cluster.adoc
@@ -1,4 +1,3 @@
-[id="getting-shell-access-to-the-openshift-cluster_{context}"]
 = Getting shell access to the {openshift} cluster
 
 To access the cluster for troubleshooting or debugging purposes, follow this procedure.

diff --git a/docs/modules/getting_started/partials/proc_installing.adoc b/docs/modules/getting_started/partials/proc_installing.adoc
@@ -1,4 +1,3 @@
-[id="installing_{context}"]
 = Installing {prod}
 
 {prod} is available as a portable executable for {rhel}.

diff --git a/docs/modules/getting_started/partials/proc_setting-up-remote-server.adoc b/docs/modules/getting_started/partials/proc_setting-up-remote-server.adoc
@@ -1,4 +1,3 @@
-[id="setting-up-remote-server_{context}"]
 = Setting up {prod} on a remote server
 
 Configure a remote server to run an {ocp} cluster provided by {prod}.

diff --git a/docs/modules/getting_started/partials/proc_setting-up.adoc b/docs/modules/getting_started/partials/proc_setting-up.adoc
@@ -1,4 +1,3 @@
-[id="setting-up_{context}"]
 = Setting up {prod}
 
 [role="_abstract"]

diff --git a/docs/modules/getting_started/partials/proc_starting-behind-proxy.adoc b/docs/modules/getting_started/partials/proc_starting-behind-proxy.adoc
@@ -1,4 +1,3 @@
-[id="starting-behind-proxy_{context}"]
 = Starting {prod} behind a proxy
 
 You can start {prod} behind a defined proxy using environment variables or configurable properties.

diff --git a/docs/modules/getting_started/partials/proc_starting-monitoring.adoc b/docs/modules/getting_started/partials/proc_starting-monitoring.adoc
@@ -1,4 +1,3 @@
-[id="starting-monitoring_{context}"]
 = Starting monitoring
 
 {prod} disables cluster monitoring by default to ensure that {prod} can run on a typical notebook.

diff --git a/docs/modules/getting_started/partials/proc_starting-the-instance.adoc b/docs/modules/getting_started/partials/proc_starting-the-instance.adoc
@@ -1,4 +1,3 @@
-[id="starting-the-instance_{context}"]
 = Starting the instance
 
 The [command]`{bin} start` command starts the {prod} instance and configured container runtime.

diff --git a/docs/modules/getting_started/partials/proc_stopping-the-instance.adoc b/docs/modules/getting_started/partials/proc_stopping-the-instance.adoc
@@ -1,4 +1,3 @@
-[id="stopping-the-instance_{context}"]
 = Stopping the instance
 
 The [command]`{bin} stop` command stops the running {prod} instance and container runtime.

diff --git a/...ules/getting_started/partials/proc_troubleshooting-bundle-version-mismatch.adoc b/...ules/getting_started/partials/proc_troubleshooting-bundle-version-mismatch.adoc
@@ -1,4 +1,3 @@
-[id="troubleshooting-bundle-version-mismatch_{context}"]
 = Troubleshooting bundle version mismatch
 
 Created {prod} instances contain bundle information and instance data.

diff --git a/...modules/getting_started/partials/proc_troubleshooting-expired-certificates.adoc b/...modules/getting_started/partials/proc_troubleshooting-expired-certificates.adoc
@@ -1,4 +1,3 @@
-[id="troubleshooting-expired-certificates_{context}"]
 = Troubleshooting expired certificates
 
 The system bundle of {ocp} in each released [command]`{bin}` executable expires 1 year after the release.

diff --git a/docs/modules/getting_started/partials/proc_troubleshooting-unknown-issues.adoc b/docs/modules/getting_started/partials/proc_troubleshooting-unknown-issues.adoc
@@ -1,4 +1,3 @@
-[id="troubleshooting-unknown-issues_{context}"]
 = Troubleshooting unknown issues
 
 Resolve most issues by restarting {prod} with a clean state.

diff --git a/docs/modules/getting_started/partials/proc_upgrading.adoc b/docs/modules/getting_started/partials/proc_upgrading.adoc
@@ -1,4 +1,3 @@
-[id="upgrading_{context}"]
 = Upgrading {prod}
 
 Newer versions of the {prod} executable require manual set up to prevent potential incompatibilities with earlier versions.

diff --git a/docs/modules/getting_started/partials/proc_viewing-configuration.adoc b/docs/modules/getting_started/partials/proc_viewing-configuration.adoc
@@ -1,4 +1,3 @@
-[id="viewing-configuration_{context}"]
 = Viewing {prod} configuration
 
 The {prod} executable provides commands to view configurable properties and the current {prod} configuration.

diff --git a/docs/modules/getting_started/partials/ref_dns-configuration.adoc b/docs/modules/getting_started/partials/ref_dns-configuration.adoc
@@ -1,7 +1,5 @@
-[id="dns-configuration_{context}"]
 = DNS configuration details
 
-[id="dns-configuration-general{context}"]
 == General DNS setup
 
 The {ocp} cluster managed by {prod} uses 2 DNS domain names, `crc.testing` and `apps-crc.testing`.
@@ -14,7 +12,6 @@ These DNS domains are served by a `dnsmasq` DNS container running inside the {pr
 The [command]`{bin} setup` command detects and adjusts your system DNS configuration so that it can resolve these domains.
 Additional checks are done to verify DNS is properly configured when running [command]`{bin} start`.
 
-[id="dns-configuration-linux_{context}"]
 == Linux
 
 On Linux, depending on your distribution, {prod} expects the following DNS configuration:

diff --git a/docs/modules/getting_started/partials/ref_minimum-system-requirements.adoc b/docs/modules/getting_started/partials/ref_minimum-system-requirements.adoc
@@ -1,10 +1,8 @@
-[id="minimum-system-requirements_{context}"]
 = Minimum system requirements
 
 [role="_abstract"]
 {prod} has the following minimum hardware and operating system requirements.
 
-[id="minimum-system-requirements-hardware_{context}"]
 == Hardware requirements
 
 {prod} is supported on these architectures:
@@ -40,7 +38,6 @@ To assign more resources to the {prod} instance, see link:{crc-gsg-url}#configur
 * 2 GB of free memory
 * 35 GB of storage space
 
-[id="minimum-system-requirements-operating-system_{context}"]
 == Operating system requirements
 
 {prod} requires the following minimum version of a supported operating system:

diff --git a/docs/modules/getting_started/partials/ref_required-software-packages.adoc b/docs/modules/getting_started/partials/ref_required-software-packages.adoc
@@ -1,4 +1,3 @@
-[id="required-software-packages_{context}"]
 = Required software packages for Linux
 
 {prod} requires the `libvirt` and `NetworkManager` packages to run on Linux.

diff --git a/docs/modules/getting_started/partials/ref_reserved-ip-subnets.adoc b/docs/modules/getting_started/partials/ref_reserved-ip-subnets.adoc
@@ -1,4 +1,3 @@
-[id="reserved-ip-subnets_{context}"]
 = Reserved IP subnets
 
 The {ocp} cluster managed by {prod} reserves IP subnets for internal use, which should not collide with your host network.