Fix Asciidoctor build warnings

[gaurav-nelson]

Fixes Asciidoctor build warnings for section title out of sequence and id assigned to section already in use.

WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 9: section title out of sequence: expected level 1, got level 2
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 24: section title out of sequence: expected level 1, got level 2
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 83: section title out of sequence: expected level 1, got level 2
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 129: section title out of sequence: expected level 1, got level 2
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 129: id assigned to section already in use: deploy_model
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 157: section title out of sequence: expected level 1, got level 2
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 303: section title out of sequence: expected level 1, got level 2
WARN  patterns/amd-rag-chat-qna/amd-rag-chat-qna-getting-started.adoc: asciidoctor: WARNING: <stdin>: line 313: section title out of sequence: expected level 1, got level 2
WARN  learn/vp_add_ops_to_pattern.adoc: asciidoctor: WARNING: <stdin>: line 13: section title out of sequence: expected level 1, got level 2
WARN  learn/vp_add_ops_to_pattern.adoc: asciidoctor: WARNING: <stdin>: line 17: section title out of sequence: expected level 1, got level 2
WARN  learn/vp_add_ops_to_pattern.adoc: asciidoctor: WARNING: <stdin>: line 21: section title out of sequence: expected level 1, got level 2

[openshift-ci]

Hi @gaurav-nelson. Thanks for your PR.

I'm waiting for a validatedpatterns 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.

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.

[mbaldessari]

This is an automated message:

You can preview this docs PR at http://588.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.

[abhatt-rh]

/lgtm