Fix typos in next.js page router username & password tutorial and oth…

…er places (#1508)

docs/pages/guides/email-and-password/basics.md

@@ -155,7 +155,7 @@ app.post("/login", async (request: Request) => {
 		// However, valid emails can be already be revealed with the signup page
 		// and a similar timing issue can likely be found in password reset implementation.
 		// It will also be much more resource intensive.
-		// Since protecting against this is none-trivial,
+		// Since protecting against this is non-trivial,
 		// it is crucial your implementation is protected against brute-force attacks with login throttling etc.
 		// If emails/usernames are public, you may outright tell the user that the username is invalid.
 		return new Response("Invalid email or password", {

docs/pages/tutorials/username-and-password/astro.md

@@ -196,7 +196,7 @@ export async function POST(context: APIContext): Promise<Response> {
 		// As a preventive measure, you may want to hash passwords even for invalid usernames.
 		// However, valid usernames can be already be revealed with the signup page among other methods.
 		// It will also be much more resource intensive.
-		// Since protecting against this is none-trivial,
+		// Since protecting against this is non-trivial,
 		// it is crucial your implementation is protected against brute-force attacks with login throttling etc.
 		// If usernames are public, you may outright tell the user that the username is invalid.
 		return new Response("Incorrect username or password", {

docs/pages/tutorials/username-and-password/nextjs-app.md

@@ -218,7 +218,7 @@ async function login(_: any, formData: FormData): Promise<ActionResult> {
 		// As a preventive measure, you may want to hash passwords even for invalid usernames.
 		// However, valid usernames can be already be revealed with the signup page among other methods.
 		// It will also be much more resource intensive.
-		// Since protecting against this is none-trivial,
+		// Since protecting against this is non-trivial,
 		// it is crucial your implementation is protected against brute-force attacks with login throttling etc.
 		// If usernames are public, you may outright tell the user that the username is invalid.
 		return {

docs/pages/tutorials/username-and-password/nextjs-pages.md

@@ -169,7 +169,7 @@ const length = new TextEncoder().encode(password).length;
 Create `pages/login.tsx` and set up a basic form.
 
 ```tsx
-// pages/signup.tsx
+// pages/login.tsx
 import { useRouter } from "next/router";
 import type { FormEvent } from "react";
 
@@ -193,7 +193,7 @@ export default function Page() {
 
 	return (
 		<>
-			<h1>Create an account</h1>
+			<h1>Sign in</h1>
 			<form method="post" action="/api/login" onSubmit={onSubmit}>
 				<label htmlFor="username">Username</label>
 				<input name="username" id="username" />
@@ -255,7 +255,7 @@ export default async function handler(req: NextApiRequest, res: NextApiResponse)
 		// As a preventive measure, you may want to hash passwords even for invalid usernames.
 		// However, valid usernames can be already be revealed with the signup page among other methods.
 		// It will also be much more resource intensive.
-		// Since protecting against this is none-trivial,
+		// Since protecting against this is non-trivial,
 		// it is crucial your implementation is protected against brute-force attacks with login throttling etc.
 		// If usernames are public, you may outright tell the user that the username is invalid.
 		res.status(400).json({

docs/pages/tutorials/username-and-password/nuxt.md

@@ -211,7 +211,7 @@ export default eventHandler(async (event) => {
 		// As a preventive measure, you may want to hash passwords even for invalid usernames.
 		// However, valid usernames can be already be revealed with the signup page among other methods.
 		// It will also be much more resource intensive.
-		// Since protecting against this is none-trivial,
+		// Since protecting against this is non-trivial,
 		// it is crucial your implementation is protected against brute-force attacks with login throttling etc.
 		// If usernames are public, you may outright tell the user that the username is invalid.
 		throw createError({

docs/pages/tutorials/username-and-password/sveltekit.md

@@ -206,7 +206,7 @@ export const actions: Actions = {
 			// As a preventive measure, you may want to hash passwords even for invalid usernames.
 			// However, valid usernames can be already be revealed with the signup page among other methods.
 			// It will also be much more resource intensive.
-			// Since protecting against this is none-trivial,
+			// Since protecting against this is non-trivial,
 			// it is crucial your implementation is protected against brute-force attacks with login throttling etc.
 			// If usernames are public, you may outright tell the user that the username is invalid.
 			return fail(400, {