Add textlint for document

[hlts2]

Description:

WHAT

As titled

WHY

We should proofread our document before publishing.

Related Issue:

How Has This Been Tested?:

Environment:

• Go Version: 1.18.3
• Docker Version: 20.10.8
• Kubernetes Version: 1.22.0
• NGT Version: 1.14.6

Types of changes:

• Bug fix [type/bug]
• New feature [type/feature]
• Add tests [type/test]
• Security related changes [type/security]
• Add documents [type/documentation]
• Refactoring [type/refactoring]
• Update dependencies [type/dependency]
• Update benchmarks and performances [type/bench]
• Update CI [type/ci]

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

Checklist:

• I have read the CONTRIBUTING document.
• I have checked open Pull Requests for the similar feature or fixes?
• I have added tests and benchmarks to cover my changes.
• I have ensured all new and existing tests passed.
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly.

[vdaas-ci]

[CHATOPS:HELP] ChatOps commands.

• 🙆‍♀️ /approve - approve
• 💌 /changelog - replace the PR body by changelog details
• 🍱 /format - format codes and add licenses
• ✅ /gen-test - generate test codes
• 🏷️ /label - add labels
• ⏪ /rebase - rebase master
• 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

[kpango]

LGTM

[kpango]

I think it would be better to sort each block in .prh.yaml by keywords to prevent duplicate additions, and for future maintainability, I think it would be better to sort them.

1. create a comment index for each possible word
2. sort the comment index
3. sort the rule definition block corresponding to the comment index

[kpango]

It would be better to divide definition block and comment block.
comment block should be located between version and rules

[kpango]

LGTM