Repository navigation
docs: move prose out of code block in Next.js guide - #924
Closed
mayur-dhavan wants to merge 1 commit into
Closed
mayur-dhavan wants to merge 1 commit into
mayur-dhavan wants to merge 1 commit into
Conversation
Contributor
Author
|
Closing as a duplicate: #913 fixes the same sentence trapped inside the code fence in the Next.js guide, and it was opened earlier. Credit to @deepanshupal for catching it first. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the Next.js getting-started guide, a sentence is trapped inside
the ts code fence, so it renders as a line of code on the live site
(between the GET and POST exports).
This moves the sentence out of the fence to become the paragraph
right after the code block. The code itself is unchanged.