Fix doc typo for Google-Sheets action: add-single-row

[RemyMachado]

WHAT

I stumbled upon a typo in the documentation

HOW

copilot:walkthrough

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

| Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **docs-v2** | ⬜️ Ignored ([Inspect](https://vercel.com/pipedreamers/docs-v2/C1WAEVGBevyCNd9RjLXYd3umrgUx)) | [Visit Preview](https://docs-v2-git-fork-remymachado-docs-typo-add-6435b4-pipedreamers.vercel.app) | | Apr 19, 2024 9:15pm | | **pipedream-docs-redirect-do-not-edit** | ⬜️ Ignored ([Inspect](https://vercel.com/pipedreamers/pipedream-docs-redirect-do-not-edit/mvMU3jAgTwycJoUU3CXp2VUfXGaD)) | [Visit Preview](https://pipedream-docs-redirect-do-not-edit-git-for-b43940-pipedreamers.vercel.app) | | Apr 19, 2024 9:15pm |

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• [ ] Create components to address specific use cases whenever possible
• [ ] Component keys should follow the format app_name_slug-slugified-component-name
• [ ] Components should follow the standard directory structure
• [ ] Prefer Node.js client libraries to REST APIs
• [ ] When making API requests, handle pagination to ensure all data / events are processed
• [ ] Use secret props to capture sensitive data
• [ ] Props and methods should be defined in app files whenever possible
• [ ] Document methods with JS Docs
• [ ] Use optional props whenever possible, and set a default value where you can
• [ ] Use async options to accept user input wherever possible

[michelle0927]

@RemyMachado Thank you for finding and fixing this! Would you mind updating the version of the package.json file? Then, I think this should be good to go.

[RemyMachado]

@RemyMachado Thank you for finding and fixing this! Would you mind updating the version of the package.json file? Then, I think this should be good to go.

Of course, sorry for the overlook! The CI/CD's even pointing out which file's causing trouble, so convenient.