fix: typos and config in HashiCorp Vault docs

[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]

All committers have signed the CLA.

[tharikaGitHub]

Hi @naduni-s,

Will you be able to add this change to the other applicable doc spaces as well? We have separate doc space branches for different APIM versions.

Thanks,
Tharika.

[naduni-s]

Hi @tharikaGitHub ,
Thanks for the feedback! I will apply the same changes to the other versioned doc branches and create separate PRs for them.