OSDOCS-22091: Fix olfconfig placeholder typo in trusted CA procedure

[kopatil2611]

Summary

• Fix placeholder typo olfconfig_cr_filename → olsconfig_cr_filename in the OpenShift Lightspeed 1.0 trusted CA certificate procedure.
• Aligns the CLI example with the olsconfig naming used elsewhere in the guide and operator docs.

Jira

https://redhat.atlassian.net/browse/OSDOCS-22091

Affected documentation

• Product: Red Hat OpenShift Lightspeed 1.0
• Guide: Configure
• Module: modules/ols-configuring-lightspeed-with-a-trusted-ca-certificate-for-the-llm.adoc
• Published URL: https://docs.redhat.com/en/documentation/red_hat_openshift_lightspeed/1.0/html-single/configure/index#ols-configuring-lightspeed-with-a-trusted-ca-certificate-for-the-llm_ols-configuring-openshift-lightspeed

Test plan

• Verified only the placeholder text changes in the trusted CA apply command
• Docs build/review as needed by the OpenShift docs team

[openshift-ci-robot]

@kopatil2611: This pull request references Jira Issue OCPBUGS-122012, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-122012 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

• Fix placeholder typo olfconfig_cr_filename → olsconfig_cr_filename in the OpenShift Lightspeed 1.0 trusted CA certificate procedure.
• Aligns the CLI example with the olsconfig naming used elsewhere in the guide and operator docs.

Jira

https://redhat.atlassian.net/browse/OCPBUGS-122012

Affected documentation

• Product: Red Hat OpenShift Lightspeed 1.0
• Guide: Configure
• Module: modules/ols-configuring-lightspeed-with-a-trusted-ca-certificate-for-the-llm.adoc
• Published URL: https://docs.redhat.com/en/documentation/red_hat_openshift_lightspeed/1.0/html-single/configure/index#ols-configuring-lightspeed-with-a-trusted-ca-certificate-for-the-llm_ols-configuring-openshift-lightspeed

Test plan

• Verified only the placeholder text changes in the trusted CA apply command
• Docs build/review as needed by the OpenShift docs team

Made with Cursor

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]

Hi @kopatil2611. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[kopatil2611]

/jira refresh

[openshift-ci-robot]

@kopatil2611: This pull request references Jira Issue OCPBUGS-122012, which is invalid:

• expected Jira Issue OCPBUGS-122012 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[kopatil2611]

whether this should be OSDOCS instead of OCPBUGS for a doc-only typo.

[openshift-ci-robot]

@kopatil2611: This pull request references OSDOCS-22091 which is a valid jira issue.

Details

In response to this:

Summary

• Fix placeholder typo olfconfig_cr_filename → olsconfig_cr_filename in the OpenShift Lightspeed 1.0 trusted CA certificate procedure.
• Aligns the CLI example with the olsconfig naming used elsewhere in the guide and operator docs.

Jira

https://redhat.atlassian.net/browse/OCPBUGS-122012

Affected documentation

• Product: Red Hat OpenShift Lightspeed 1.0
• Guide: Configure
• Module: modules/ols-configuring-lightspeed-with-a-trusted-ca-certificate-for-the-llm.adoc
• Published URL: https://docs.redhat.com/en/documentation/red_hat_openshift_lightspeed/1.0/html-single/configure/index#ols-configuring-lightspeed-with-a-trusted-ca-certificate-for-the-llm_ols-configuring-openshift-lightspeed

Test plan

• Verified only the placeholder text changes in the trusted CA apply command
• Docs build/review as needed by the OpenShift docs team

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.

[kopatil2611]

/jira refresh

[openshift-ci-robot]

@kopatil2611: This pull request references OSDOCS-22091 which is a valid jira issue.

Details

In response to this:

/jira refresh

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.