Fix spelling errors in documentation

[emilysunaryo]

Description

In this PR, I edited 3 typos in the pushdown.md documents.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Emily Sunaryo.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[ebyhr]

Could you fix the same typo in json.md?

[mosabua]

@emilysunaryo ?

[mosabua]

You can just do a global search for that typo and fix all of them in this PR

[mosabua]

Please fix commit message to follow https://trino.io/development/process#contribution-process .. specifically https://cbea.ms/git-commit/

Once CLA is processed we can merge.

[ebyhr]

Please fix commit message

The current commit title looks good to me. What's your suggestion?

[mosabua]

Please fix commit message

The current commit title looks good to me. What's your suggestion?

Typically commit message should not talk about what file is affected .. especially also since you might add other files. You could do something like

Fix spelling errors in documentation or Correct spelling in docs or Fix grammar issues in docs or similar.

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Emily Sunaryo.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Emily Sunaryo.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[mosabua]

@cla-bot check

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Emily Sunaryo.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[mosabua]

Looks good now. Thank you.