8000 fix(docs): correct API route reference from Nest to Next.js by BugeezAvsit · Pull Request #375 · temporalio/temporal-learning · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix(docs): correct API route reference from Nest to Next.js #375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

BugeezAvsit
Copy link

The tutorial incorrectly refers to "Nest API Routes" instead of "Next.js API Routes". This commit updates the text to accurately reflect that the API routes are implemented using Next.js, ensuring consistency with the rest of the guide.

What was changed

  • Updated all occurrences of "Nest API Routes" to "Next.js API Routes" in the tutorial content.
  • Verified that code examples and supporting text now consistently refer to Next.js.

Why?

  • To remove confusion for readers by ensuring the documentation correctly reflects that the API routes are built with Next.js, not Nest.js.
  • To maintain consistency between the tutorial content and the code examples provided.

Checklist

  1. Closes

  2. How was this tested:

    • Reviewed the rendered documentation to confirm that the references now correctly say "Next.js API Routes".
    • Ensured consistency across all code examples and textual descriptions.
  3. Any docs updates needed?

    • No additional documentation updates needed beyond this change.

The tutorial incorrectly refers to "Nest API Routes" instead of "Next.js API Routes". This commit updates the text to accurately reflect that the API routes are implemented using Next.js, ensuring consistency with the rest of the guide.
@BugeezAvsit BugeezAvsit requested a review from a team as a code owner April 1, 2025 09:23
Copy link
vercel bot commented Apr 1, 2025

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

Name Status Preview Comments Updated (UTC)
temporal-learning ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 1, 2025 9:24am

@CLAassistant
Copy link
CLAassistant commented Apr 1, 2025

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0