github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #9160] [MERGED] docs: correct wording for invocable endpoints in integration guides #25375

New Issue
Closed
opened 2026-04-15 22:51:33 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 22:51:33 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/9160
Author: @Jadenstanton
Created: 4/14/2026
Status: ✅ Merged
Merged: 4/14/2026
Merged by: @ping-maxwell

Base: main ← Head: main

📝 Commits (1)

  • f76d427 docs: correct wording for invocable endpoints in integration guides

📊 Changes

3 files changed (+3 additions, -3 deletions)

View changed files

📝 docs/content/docs/integrations/next.mdx (+1 -1)
📝 docs/content/docs/integrations/nuxt.mdx (+1 -1)
📝 docs/content/docs/integrations/waku.mdx (+1 -1)

📄 Description

Fixed a repeated grammatical error across three documentation pages. "a invocable" has been corrected to "is invocable" in each instance, as "invocable" requires "is" rather than the indefinite article "a."
No breaking changes. No related issues.

Summary by cubic

Fixes a grammatical error in the Next, Nuxt, and Waku integration docs by replacing “a invocable” with “is invocable” in the endpoint description.

Written for commit f76d427475. Summary will update on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/9160 **Author:** [@Jadenstanton](https://github.com/Jadenstanton) **Created:** 4/14/2026 **Status:** ✅ Merged **Merged:** 4/14/2026 **Merged by:** [@ping-maxwell](https://github.com/ping-maxwell) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`f76d427`](https://github.com/better-auth/better-auth/commit/f76d427475d9d68d2003e553d015b14563b1f3d8) docs: correct wording for invocable endpoints in integration guides ### 📊 Changes **3 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/integrations/next.mdx` (+1 -1) 📝 `docs/content/docs/integrations/nuxt.mdx` (+1 -1) 📝 `docs/content/docs/integrations/waku.mdx` (+1 -1) </details> ### 📄 Description Fixed a repeated grammatical error across three documentation pages. "a invocable" has been corrected to "is invocable" in each instance, as "invocable" requires "is" rather than the indefinite article "a." No breaking changes. No related issues. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Fixes a grammatical error in the `Next`, `Nuxt`, and `Waku` integration docs by replacing “a invocable” with “is invocable” in the endpoint description. <sup>Written for commit f76d427475d9d68d2003e553d015b14563b1f3d8. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 22:51:33 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#25375
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?