Typo error corrected and inconsistency removed!

[AgniveshChaubey]

What does this PR do?

This PR fixes the typo error and inconsistency mentioned in #34291

Before:
"description": "Overview dashboard por powershell module."
"title": "[Winlogbeat powershell] Overview",

After:
"description": "Overview dashboard for PowerShell module.",
"title": "[Winlogbeat PowerShell] Overview",

Signed-off by : Agnivesh Chaubey [email protected]

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @AgniveshChaubey? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-26T21:41:11.811+0000

• Duration: 37 min 35 sec

Test stats 🧪

Test	Results
Failed	0
Passed	336
Skipped	0
Total	336

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[efd6]

/test

[AgniveshChaubey]

/test

can you please explain a bit more about what are you referring to?

[efd6]

@AgniveshChaubey Only CI-approved contributors can start builds. To get your build started, I asked the builder to start with the /test command.

[efd6]

/test

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[efd6]

Would you mind reverting this addition please.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b typo-error-correction/#34291-1 upstream/typo-error-correction/#34291-1
git merge upstream/main
git push upstream typo-error-correction/#34291-1

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b typo-error-correction/#34291-1 upstream/typo-error-correction/#34291-1
git merge upstream/main
git push upstream typo-error-correction/#34291-1

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @AgniveshChaubey? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform)

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b typo-error-correction/#34291-1 upstream/typo-error-correction/#34291-1
git merge upstream/main
git push upstream typo-error-correction/#34291-1