fix: various typos

README.md

@@ -43,7 +43,7 @@ To add a game to the drop library, do as follows:
 6. Navigate to http://your.drop.server.ip:3000/
 7. Import game metadata (uses GiantBomb API Key) by selecting the game and specifying which entry to import
 8. Navigate to http://your.drop.server.ip:3000/admin/library
-9. You should see the game which you have just imported listed in this menu. There should be a notification that "Drop has detected you have new verions of this game to import". Select import here.
+9. You should see the game which you have just imported listed in this menu. There should be a notification that "Drop has detected you have new versions of this game to import". Select import here.
 10. Select the game version to import and thus fill in fields as required.
 
 ## Tech Stack

server/internal/acls/descriptions.ts

@@ -19,7 +19,7 @@ export const userACLDescriptions: ObjectFromList<typeof userACLs> = {
 
   "notifications:read": "Fetch this account's notifications.",
   "notifications:mark": "Mark notifications as read for this account.",
-  "notifications:listen": "Connect to a websocket to recieve notifications.",
+  "notifications:listen": "Connect to a websocket to receive notifications.",
   "notifications:delete": "Delete this account's notifications.",
 
   "screenshots:new": "Create screenshots for this account",

server/internal/clients/README.md

@@ -16,7 +16,7 @@ Server sends redirect to `drop://handshake/[id]/[token]`, where the token is an
 
 ## 3. Client requests certificates
 
-Client makes request: `POST /api/v1/client/auth/handshake` with the token recieved in the previous step.
+Client makes request: `POST /api/v1/client/auth/handshake` with the token received in the previous step.
 
 The server uses it's CA to generate a public-private key pair, the CN of the client ID. It then sends that pair, plus the CA's public key, to the client, which stores it all.
 

server/internal/notifications/index.ts

@@ -1,5 +1,5 @@
 /*
-The notification system handles the recieving, creation and sending of notifications in Drop
+The notification system handles the receiving, creation and sending of notifications in Drop
 
 Design goals:
 1. Nonce-based notifications; notifications should only be created once

server/internal/objects/objectHandler.ts

@@ -195,7 +195,7 @@ export class ObjectHandler {
    * @returns
    * @description If we need to fetch a remote resource, it doesn't make sense
    * to immediately fetch the object, *then* check permissions.
-   * Instead the caller can pass a simple anonymous funciton, like
+   * Instead the caller can pass a simple anonymous function, like
    * () => $dropFetch('/my-image');
    * And if we actually have permission to write, it fetches it then.
    */

server/internal/tasks/index.ts

@@ -41,7 +41,7 @@ type TaskPoolEntry = FinishedTask & {
  * easily without re-inventing the wheel every time.
  */
 class TaskHandler {
-  // registry of schedualed tasks to be created
+  // registry of scheduled tasks to be created
   private taskCreators: Map<TaskGroup, () => Task> = new Map();
 
   // list of all currently running tasks

server/plugins/01.system-init.ts

@@ -3,7 +3,7 @@ import prisma from "~/server/internal/db/database";
 export default defineNitroPlugin(async (_nitro) => {
   // Ensure system user exists
   // The system user owns any user-based code
-  // that we want to re-use for the app
+  // that we want to reuse for the app
   // e.g. notifications
   await prisma.user.upsert({
     where: {