docs: fix misspelled 'descrition' front-matter key and a typo

[vaibhav8a]

Summary

Changes

Three feature docs pages open with a misspelled front-matter key:

---
title: Parser
descrition: Utility
---

descrition is not a key MkDocs recognises, and every other feature page uses description: — logger.md, tracer.md and metrics.md all read description: Core utility.

The effect is not cosmetic. Because the key never resolves, docs/features/parser.md, docs/features/signer.md and docs/features/validation.md are published with no description metadata at all, so <meta name="description"> falls back to the site default. That is what search engines and link previews read, so those three pages are less discoverable than their siblings.

This corrects the key to description: on all three, leaving the values untouched.

It also fixes a plain prose typo in docs/features/event-handler/appsync-graphql.md line 92: "It's recommended to pass a refernce" → reference.

Docs only — no source, tests or public API are touched.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #5583

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[svozza]

Hi there, thank you for the PR. Can you please create an accompanying GitHub issue for this pull request? Ideally we prefer these to be created before any PR. Please see step 3 in the contributing guide: https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CONTRIBUTING.md#contributing-via-pull-requests. Also, can you update the PR body to use the template we have? If you are using a coding agent, just ask it to invoke the create-issue and create-pr skills.

[vaibhav8a]

Thanks @svozza — both done.

• Issue: Docs: three feature pages publish no description metadata (misspelled front-matter key) #5583, using the documentation-improvements template. Apologies for the ordering; I opened the PR before reading step 3 of the contributing guide.
• PR body: rewritten to the template, with closes #5583.

Understood that a PR against a non-triaged issue may not go anywhere. Happy to wait on triage, and equally happy for this to be closed if you'd rather handle the front-matter differently — the substance is that those three pages currently publish no <meta name="description"> at all, however you choose to fix it.

[svozza]

LGTM. Merging!

[powertools-for-aws-oss-automation]

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!