Correct a few spelling mistakes

__fixtures__/test-project/api/src/functions/auth.ts

@@ -64,14 +64,14 @@ export const handler = async (event, context) => {
 
   const resetPasswordOptions = {
     // handler() is invoked after the password has been successfully updated in
-    // the database. Returning anything truthy will automatically logs the user
+    // the database. Returning anything truthy will automatically log the user
     // in. Return `false` otherwise, and in the Reset Password page redirect the
     // user to the login page.
     handler: (user) => {
       return user
     },
 
-    // If `false` then the new password MUST be different than the current one
+    // If `false` then the new password MUST be different from the current one
     allowReusedPassword: true,
 
     errors: {
@@ -125,7 +125,7 @@ export const handler = async (event, context) => {
     db: db,
 
     // The name of the property you'd call on `db` to access your user table.
-    // ie. if your Prisma model is named `User` this value would be `user`, as in `db.user`
+    // i.e. if your Prisma model is named `User` this value would be `user`, as in `db.user`
     authModelAccessor: 'user',
 
     // A map of what dbAuth calls a field to what your database calls it.

docs/docs/connection-pooling.md

@@ -24,7 +24,7 @@ To use Prisma Client with PgBouncer from a serverless function, add the `?pgboun
 postgresql://USER:PASSWORD@HOST:PORT/DATABASE?pgbouncer=true
 ```
 
-Typically, your PgBouncer port will be 6543 which is different than the Postgres default of 5432.
+Typically, your PgBouncer port will be 6543 which is different from the Postgres default of 5432.
 
 > Note that since Prisma Migrate uses database transactions to check out the current state of the database and the migrations table, if you attempt to run Prisma Migrate commands in any environment that uses PgBouncer for connection pooling, you might see an error.
 >

docs/docs/how-to/supabase-auth.md

@@ -36,7 +36,7 @@ So, just this once, I hereby give you permission to fire-up Create React App as
 >
 > If you're like me—and I'm pretty sure I'm just human—you may find yourself spinning in jumbled auth jargon. Hang in there, you'll get your auth ducks lined up eventually.
 >
-> I'm proud to tell you that I now know that the Redwood Supabase auth client wraps the Supabase GoTrueJS client, which is a fork of Netlify’s GoTrueJS client (which is different than Netlify Identity). And dbAuth is a totally separate auth option. Plus, I'll keep it simple and not use RBAC at the moment.
+> I'm proud to tell you that I now know that the Redwood Supabase auth client wraps the Supabase GoTrueJS client, which is a fork of Netlify’s GoTrueJS client (which is different from Netlify Identity). And dbAuth is a totally separate auth option. Plus, I'll keep it simple and not use RBAC at the moment.
 >
 > Ahhh! It took me a few weeks to figure this out.
 

docs/docs/testing.md

@@ -847,7 +847,7 @@ Two situations make testing Cells unique:
 1. A single Cell can export up to four separate components
 2. There's a GraphQL query taking place
 
-The first situation is really no different than regular component testing: you just test more than one component in your test. For example:
+The first situation is really no different from regular component testing: you just test more than one component in your test. For example:
 
 ```jsx title="web/src/components/ArticleCell/ArticleCell.js"
 import Article from 'src/components/Article'

packages/cli/src/commands/setup/auth/templates/dbAuth.function.ts.template

@@ -64,14 +64,14 @@ export const handler = async (event, context) => {
 
   const resetPasswordOptions = {
     // handler() is invoked after the password has been successfully updated in
-    // the database. Returning anything truthy will automatically logs the user
+    // the database. Returning anything truthy will automatically log the user
     // in. Return `false` otherwise, and in the Reset Password page redirect the
     // user to the login page.
     handler: (user) => {
       return user
     },
 
-    // If `false` then the new password MUST be different than the current one
+    // If `false` then the new password MUST be different from the current one
     allowReusedPassword: true,
 
     errors: {
@@ -125,7 +125,7 @@ export const handler = async (event, context) => {
     db: db,
 
     // The name of the property you'd call on `db` to access your user table.
-    // ie. if your Prisma model is named `User` this value would be `user`, as in `db.user`
+    // i.e. if your Prisma model is named `User` this value would be `user`, as in `db.user`
     authModelAccessor: 'user',
 
     // A map of what dbAuth calls a field to what your database calls it.

packages/graphql-server/src/plugins/useRedwoodLogger.ts

@@ -27,7 +27,7 @@ import { RedwoodGraphQLContext } from '../functions/types'
 type GraphQLLoggerOptions = {
   /**
    * Sets log level for GraphQL logging.
-   * This level setting can be different than the one used in api side logging.
+   * This level setting can be different from the one used in api side logging.
    * Defaults to the same level as the logger unless set here.
    *
    * Available log levels:

packages/record/src/redwoodrecord/Core.js

@@ -9,7 +9,7 @@ export default class Core {
 
   // Set in child class to override DB accessor name. This is the name of the
   // property you would call on an instance of Prisma Client in order the query
-  // a model in your schema. ie. For the call `db.user` the accessorName is
+  // a model in your schema. i.e. For the call `db.user` the accessorName is
   // "user". Not setting this property will use the default camelCase version of
   // the class name itself as the accessor.
   //