Skip to content

OSDOCS-18265: Vale DITA fixes for OSD storage#109019

Open
bhardesty wants to merge 1 commit intoopenshift:mainfrom
bhardesty:osdocs-18265-vale-fixes-osd-storage
Open

OSDOCS-18265: Vale DITA fixes for OSD storage#109019
bhardesty wants to merge 1 commit intoopenshift:mainfrom
bhardesty:osdocs-18265-vale-fixes-osd-storage

Conversation

@bhardesty
Copy link
Contributor

@bhardesty bhardesty commented Mar 25, 2026

This PR addresses the Vale DITA fixes for the OSD content in the Storage book. It does not address any Vale issues for non-OSD content.

Version(s):

  • 4.21+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-18265

Link to docs preview:

QE review:

  • n/a

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 25, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 25, 2026

@bhardesty: This pull request references OSDOCS-18265 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR addresses the Vale DITA fixes for the OSD content in the Storage book. It does not address any Vale issues for non-OSD content.

Version(s):

  • 4.21+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-18265

Link to docs preview:
*

QE review:

  • n/a

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 25, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 25, 2026

@bhardesty: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 25, 2026

@bhardesty: This pull request references OSDOCS-18265 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR addresses the Vale DITA fixes for the OSD content in the Storage book. It does not address any Vale issues for non-OSD content.

Version(s):

  • 4.21+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-18265

Link to docs preview:

QE review:

  • n/a

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

--
where:

`Statement.Principal.Federated`:: Specify your AWS account ID and the OpenShift OIDC provider endpoint.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To knowledge, the best practice is to use the word "Specifies" rather than an infinitive "Specify". At least "specifies" is used in the Example use cases in the Callout replacement for OCP docs doc.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed - let's switch it to "Specifies"

role_arn = <role_ARN>
web_identity_token_file = /var/run/secrets/openshift/serviceaccount/token
----
<1> Replace `role_ARN` with the output you saved while creating the role.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to confirm that this callout can be deleted entirely and doesn't need to be replaced?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's pretty self-evident for users so, I am cool with dropping this explanation.

@otikhomi
Copy link
Contributor

otikhomi commented Mar 25, 2026

@bhardesty The preview is looking good. Left a couple of questions.

Do I get it correctly that other CQA fixes are out of scope of this PR? E.g. a short description uses self-referential language (This procedure explains how to...) or a prereqs list doesn't need periods at the end of items that are incomplete sentences (in a module one item has a period).

Copy link
Contributor

@EricPonvelle EricPonvelle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

--
where:

`Statement.Principal.Federated`:: Specify your AWS account ID and the OpenShift OIDC provider endpoint.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed - let's switch it to "Specifies"

role_arn = <role_ARN>
web_identity_token_file = /var/run/secrets/openshift/serviceaccount/token
----
<1> Replace `role_ARN` with the output you saved while creating the role.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's pretty self-evident for users so, I am cool with dropping this explanation.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.21 branch/enterprise-4.22 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants