Skip to content

Commit aa9e9c9

Browse files
committed
OSDOCS#15507: Removing discrete headings in core OCP docs
1 parent f868414 commit aa9e9c9

File tree

173 files changed

+1037
-1037
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

173 files changed

+1037
-1037
lines changed

architecture/architecture-installation.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ include::modules/installation-process.adoc[leveloffset=+2]
1919
2020
* xref:../scalability_and_performance/recommended-performance-scale-practices/recommended-control-plane-practices.adoc#master-node-sizing_recommended-control-plane-practices[Control plane node sizing]
2121
22-
[discrete]
22+
2323
=== Installation scope
2424

2525
The scope of the {product-title} installation program is intentionally narrow. It is designed for simplicity and ensured success. You can complete many more configuration tasks after installation completes.

authentication/identity_providers/configuring-request-header-identity-provider.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,8 @@ include::modules/identity-provider-add.adoc[leveloffset=+1]
3030
This example configures an Apache authentication proxy for the {product-title}
3131
using the request header identity provider.
3232

33-
[discrete]
33+
3434
include::modules/identity-provider-apache-custom-proxy-configuration.adoc[leveloffset=+2]
3535

36-
[discrete]
36+
3737
include::modules/identity-provider-configuring-apache-request-header.adoc[leveloffset=+2]

hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ include::modules/hcp-bm-add-nodes-to-inventory.adoc[leveloffset=+2]
6262

6363
include::modules/hcp-bm-create-infra-console.adoc[leveloffset=+2]
6464

65-
[discrete]
65+
6666
[role="_additional-resources"]
6767
[id="addl-res-hcp-bm-infra-console_{context}"]
6868
=== Additional resources

installing/installing_bare_metal/ipi/ipi-install-installation-workflow.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ include::modules/ipi-install-configuring-storage-on-nodes.adoc[leveloffset=+2]
188188
// Creating a disconnected registry
189189
include::modules/ipi-install-creating-a-disconnected-registry.adoc[leveloffset=+1]
190190

191-
[discrete]
191+
192192
[id="prerequisites_ipi-disconnected-registry"]
193193
=== Prerequisites
194194

installing/installing_sno/install-sno-installing-sno.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ Installing a single-node cluster on {ibm-z-name} and {ibm-linuxone-name} require
154154
Installing a single-node cluster on {ibm-z-name} simplifies installation for development and test environments and requires less resource requirements at entry level.
155155
====
156156

157-
[discrete]
157+
158158
=== Hardware requirements
159159

160160
* The equivalent of two Integrated Facilities for Linux (IFL), which are SMT2 enabled, for each cluster.
@@ -181,7 +181,7 @@ Installing a single-node cluster on {ibm-power-name} requires user-provisioned i
181181
Installing a single-node cluster on {ibm-power-name} simplifies installation for development and test environments and requires less resource requirements at entry level.
182182
====
183183

184-
[discrete]
184+
185185
=== Hardware requirements
186186

187187
* The equivalent of two Integrated Facilities for Linux (IFL), which are SMT2 enabled, for each cluster.

installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ include::modules/agent-installer-fips-compliance.adoc[leveloffset=+1]
5555
//Configuring FIPS through the Agent-based Installer
5656
include::modules/agent-installer-configuring-fips-compliance.adoc[leveloffset=+1]
5757

58-
[discrete]
58+
5959
[role="_additional-resources"]
6060
.Additional resources
6161

installing/overview/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ include::modules/ipi-verifying-nodes-after-installation.adoc[leveloffset=+2]
3636
3737
* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform[Assisted Installer for OpenShift Container Platform]
3838
39-
[discrete]
39+
4040
=== Installation scope
4141

4242
The scope of the {product-title} installation program is intentionally narrow. It is designed for simplicity and ensured success. You can complete many more configuration tasks after installation completes.

machine_management/creating_machinesets/creating-machineset-vsphere.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,15 @@ include::modules/machineset-vsphere-required-permissions.adoc[leveloffset=+1]
2020
include::modules/compute-machineset-upi-reqs.adoc[leveloffset=+1]
2121

2222
//Obtaining the infrastructure ID
23-
[discrete]
23+
2424
include::modules/machineset-upi-reqs-infra-id.adoc[leveloffset=+2]
2525

2626
//Satisfying vSphere credentials requirements
27-
[discrete]
27+
2828
include::modules/machineset-upi-reqs-vsphere-creds.adoc[leveloffset=+2]
2929

3030
//Satisfying ignition configuration requirements
31-
[discrete]
31+
3232
include::modules/machineset-upi-reqs-ignition-config.adoc[leveloffset=+2]
3333
[role="_additional-resources"]
3434
.Additional resources

0 commit comments

Comments
 (0)