Fix/hashicorp vault docs v4.2.0

[naduni-s]

Purpose

Fixes several typos, and a Log4j2 property key in the HashiCorp Vault integration documentation.

Goals

Correct spelling mistakes (“Intergrate” → “Integrate”, “Hashicrop” → “HashiCorp”, “methords” → “methods”, “requirment” → “requirement”).

Fix Log4j2 property syntax:
logger.org-wso2-carbon-securevault-hashicorp.appenderRefCARBON_CONSOLE.ref
→ logger.org-wso2-carbon-securevault-hashicorp.appenderRef.CARBON_CONSOLE.ref

Approach

Edited the Markdown file:
en/docs/install-and-setup/setup/security/logins-and-passwords/harshicrop-vault-extension.md
Applied the corrections directly to the text and configuration examples.
No UI changes; no screenshots required.

User stories

As a developer, I want the documentation to be accurate, so I can set up HashiCorp Vault integration without confusion or errors.>

Release note

Fixes typos and configuration instructions in the HashiCorp Vault integration documentation page.

Documentation

This PR updates the official WSO2 API Manager docs: [https://apim.docs.wso2.com/en/latest/install-and-setup/setup/security/logins-and-passwords/harshicrop-vault-extension/]

Training

N/A – no training content affected.

Certification

N/A – no certification impact.

Marketing

N/A – no marketing content affected.

Automation tests

• Unit tests

  N/A

• Integration tests

  N/A

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
• Ran FindSecurityBugs plugin and verified report? N/A
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

N/A

Test environment

Not applicable – documentation-only change.

Learning

Verified spelling and configuration with official WSO2 guides.
Checked Log4j2 syntax against working APIM setup to ensure correctness.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
16 out of 19 committers have signed the CLA.

✅ BiyonFernando
✅ AnuGayan
✅ Thenujan-Nagaratnam
✅ Tharanidk
✅ PasanT9
✅ thivindu
✅ NethmiRanasinghe
✅ thisaltennakoon
✅ kavindasr
✅ DinithHerath
✅ HeshanSudarshana
✅ ashera96
✅ SavinduDimal
✅ RusJaI
✅ naduni-s
✅ dushaniw
❌ tharikaGitHub
❌ Naduni Pamudika
❌ npamudika

---

Naduni Pamudika seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[tharikaGitHub]

@naduni-s,

You will have to checkout locally to the respective branch for example 4.2.0 in this repo and send a PR. This has detected unwanted commits. Let's address the same in the following PRs as well. Also let's send a PR to 4.6.0 branch.

1. Fix/hashicorp vault docs v4.5.0 #9674
2. Fix/hashicorp vault docs v4.4.0 #9673
3. Fix/hashicorp vault docs v4.3.0 #9672

Thanks,
Tharika

[tharikaGitHub]

Hi @naduni-s,

I will close this PR due to inactivity. Please reopen once the concerns are addressed.

Thanks,
Tharika.