Skip to content

Commit f6ba8ae

Browse files
committed
OSDOCS-8337: temp revise short attribute
1 parent af50724 commit f6ba8ae

File tree

8 files changed

+12
-13
lines changed

8 files changed

+12
-13
lines changed

_attributes/attributes-microshift.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,9 @@
66
:OCP: OpenShift Container Platform
77
:ocp-version: 4.14
88
:oc-first: pass:quotes[OpenShift CLI (`oc`)]
9-
:product-title-first: Red Hat build of MicroShift (MicroShift)
10-
:microshift-short: MicroShift
9+
//:product-title-first: Red Hat build of MicroShift (MicroShift)
10+
:microshift-short: Red Hat build of MicroShift
11+
//note that microshift-short was updated to the long form pending an approved short form
1112
:product-registry: OpenShift image registry
1213
:product-version: 4.14
1314
:rhel-major: rhel-9

_topic_maps/_topic_map_ms.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Distros: microshift
7777
Topics:
7878
- Name: The etcd service
7979
File: microshift-etcd
80-
- Name: The sos tool
80+
- Name: The sos report tool
8181
File: microshift-sos-report
8282
---
8383
Name: API reference

microshift_install/microshift-embed-in-rpm-ostree.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,6 @@ toc::[]
88

99
You can embed {microshift-short} into a {op-system-ostree-first} {op-system-version} image. Use this guide to build a {op-system} image containing {microshift-short}.
1010

11-
//include::snippets/microshift-tech-preview-snip.adoc[leveloffset=+1]
12-
1311
include::modules/microshift-preparing-for-image-building.adoc[leveloffset=+1]
1412

1513
include::modules/microshift-adding-repos-to-image-builder.adoc[leveloffset=+1]

microshift_install/microshift-install-rpm.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
:_content-type: ASSEMBLY
22
[id="microshift-install-rpm"]
3-
= Installing {microshift-short} from an RPM package
3+
= Installing from an RPM package
44
include::_attributes/attributes-microshift.adoc[]
55
:context: microshift-install-rpm
66

microshift_support/microshift-etcd.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
:_content-type: ASSEMBLY
22
[id="microshift-etcd"]
3-
= Using etcd
3+
= The etcd service
44
include::_attributes/attributes-microshift.adoc[]
55
:context: microshift-etcd
66

77
toc::[]
88

99
[role="_abstract"]
10-
{product-title} etcd is delivered as part of the {microshift-short} RPM. The etcd service is run as a separate process and the lifecycle is managed automatically by {microshift-short}.
10+
The etcd service is delivered as part of the {product-title} RPM. The etcd service is run as a separate process and the lifecycle is managed automatically by {product-title}.
1111

1212
include::modules/microshift-observe-debug-etcd-server.adoc[leveloffset=+1]
1313

modules/microshift-check-cluster-status.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@
44

55
:_content-type: PROCEDURE
66
[id="microshift-check-cluster-status_{context}"]
7-
= Checking the status of a {microshift-short} cluster
7+
= Checking the status of a cluster
88

99
You can check the status of a {microshift-short} cluster or see active pods by running a simple command. Given in the following procedure are three commands you can use to check cluster status. You can choose to run one, two, or all commands to help you retrieve the information you need to troubleshoot the cluster.
1010

1111
.Procedure
12-
* You can check the {microshift-short} system status, which returns the cluster status, by running the following command:
12+
* You can check the system status, which returns the cluster status, by running the following command:
1313
+
1414
[source,terminal]
1515
----
@@ -18,7 +18,7 @@ $ sudo systemctl status microshift
1818
+
1919
If {microshift-short} is failing to start, this command returns the logs from the previous run.
2020
21-
* Optional: You can view the {microshift-short} logs by running the following command:
21+
* Optional: You can view the logs by running the following command:
2222
+
2323
[source,terminal]
2424
----

modules/microshift-config-etcd.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
:_content-type: PROCEDURE
66
[id="microshift-config-etcd_{context}"]
7-
= Configuring the memoryLimitMB value to set parameters for the {microshift-short} etcd server
7+
= Configuring the memoryLimitMB value to set parameters for the etcd server
88

99
By default, etcd will use as much memory as necessary to handle the load on the system. In some memory constrained systems, it might be necessary to limit the amount of memory etcd is allowed to use at a given time.
1010

modules/microshift-version-cli.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
:_content-type: PROCEDURE
66
[id="microshift-version-cli_{context}"]
7-
= Checking the {microshift-short} version using the command-line interface
7+
= Checking the version using the command-line interface
88

99
To begin troubleshooting, you must know your {microshift-short} version. One way to get this information is by using the CLI.
1010

0 commit comments

Comments
 (0)