docs: We have twice the word "side" (nextauthjs#964)

* chore: use stale label, instead of wontfix * chore: add link to issue explaining stalebot * chore: fix typo in stalebot comment * chore: run build GitHub Action on canary also * chore: run build GitHub Actions on canary as well * chore: add reproduction section to questions * feat(provider): Add Azure Active Directory B2C (nextauthjs#809) * add provider: Microsoft * documentation * support no tenant setup * fix code style * chore: rename Microsoft provider to AzureADB2C * chore: alphabetical order in providers/index * Revert "feat(provider): Add Azure Active Directory B2C (nextauthjs#809)" (nextauthjs#919) This reverts commit 6e6a24a. * chore: add myself to the contributors list 🙈 * We have twice the word "side" Co-authored-by: Balázs Orbán <[email protected]> Co-authored-by: Vladimir Evdokimov <[email protected]>
mnphpexpert · Feb 1, 2021 · fa187d4 · fa187d4
1 parent 5c29ff8
commit fa187d4
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/www/docs/tutorials/securing-pages-and-api-routes.md b/www/docs/tutorials/securing-pages-and-api-routes.md
@@ -3,7 +3,7 @@ id: securing-pages-and-api-routes
 title: Securing pages and API routes
 ---
 
-You can easily protect client and server side side rendered pages and API routes with NextAuth.js.
+You can easily protect client and server side rendered pages and API routes with NextAuth.js.
 
 _You can find working examples of the approaches shown below in the [example project](https://github.com/iaincollins/next-auth-example/)._