fix spelling

Author: mythz

content/docs/autoquery/crud.mdx

@@ -120,14 +120,14 @@ public class DeleteRockstar : IDeleteDb<Rockstar>, IReturnVoid
 }
 ```
 
-and to Query the Rockstar table you have the [full featureset of AutoQuery](/docs/autoquery) for a complete set 
+and to Query the Rockstar table you have the [full feature-set of AutoQuery](/docs/autoquery) for a complete set 
 of CRUD Services without needing to provide any implementations.
 
 ## Custom AutoQuery CRUD Implementation
 
 Just as you can create [Custom AutoQuery Implementations](/docs/autoquery#custom-autoquery-implementations) 
 to override the default AutoQuery behavior you can also override AutoQuery CRUD implementations by creating 
-implementations with AutoQuery CRUD Request DTOs and calling the relevate `IAutoQueryDb` method, e.g:
+implementations with AutoQuery CRUD Request DTOs and calling the relevant `IAutoQueryDb` method, e.g:
 
 ```csharp
 public class MyCrudServices(IAutoQueryDb autoQuery) : Service
@@ -324,7 +324,7 @@ public class MyScripts : ScriptMethods
 
 // Populate Post.TenantId property with `tenantId` #Script Method
 [AutoPopulate(nameof(Post.TenantId), Eval = "tenantId")]
-public class CreatePost : ICreatDb<Post>, IReturn<IdResponse> 
+public class CreatePost : ICreateDb<Post>, IReturn<IdResponse> 
 {
     public string Name { get; set; }
     public string Content { get; set; }

content/docs/autoquery/querying.mdx

@@ -37,7 +37,7 @@ To switch from SQLite to PostgreSQL/SQL Server/MySQL:
 npx add-in ef-postgres
 ```
 
-2. Optionally install `db-identity` to use this RBMDS in background jobs and Request Logs:
+2. Optionally install `db-identity` to use this RDBMS in background jobs and Request Logs:
 
 ```bash
 npx add-in db-identity
@@ -102,9 +102,9 @@ Which just like other Request DTO's in ServiceStack falls back to using ServiceS
 
 This is possible as a hidden gem in AutoQuery's approach is that everything still works whether using explicit or no properties (implicit). This is possible as the JsonServiceClient generates the same HTTP Request that matches the implicit conventions whether the property exist on the Server Request DTO or not.
 
-#### Explcit Request DTO Properties Recommended
+#### Explicit Request DTO Properties Recommended
 
-In order for ServiceStack to generate typed Properties for your AutoQuery API in its [TypeScript DTOs](https://docs.servicestack.net/typescript-add-servicestack-reference) they would need to defined explitly on your Request DTO, this also gives AI Models necessary context for determining what properties are available for each .NET API.
+In order for ServiceStack to generate typed Properties for your AutoQuery API in its [TypeScript DTOs](https://docs.servicestack.net/typescript-add-servicestack-reference) they would need to defined explicitly on your Request DTO, this also gives AI Models necessary context for determining what properties are available for each .NET API.
 
 ## Implicit Conventions
 
@@ -730,7 +730,7 @@ that you can add when specifying custom fields is `ExcludeDefaultValues`, e.g:
 ```
 
 Using TypeScript `JsonServiceClient` you can include additional queryString parameters that are not defined 
-on Request DTOs using the 2nd `args` paramater. e.g:
+on Request DTOs using the 2nd `args` parameter. e.g:
 
 ```ts
 const api = await client.api(request, { jsconfig: 'ExcludeDefaultValues' })

content/docs/claude.mdx

@@ -124,7 +124,7 @@ npx okai rm Table.d.ts
 ### Hybrid Development/Production Model
 
 **Development Mode:**
-- `dotnet watch` from MyApp starts .NET (port 5001) and Next.js dev server (port 3000), accesible via `https://localhost:5001`
+- `dotnet watch` from MyApp starts .NET (port 5001) and Next.js dev server (port 3000), accessible via `https://localhost:5001`
 - ASP.NET Core proxies requests to Next.js dev server via `NodeProxy` (configured in [Program.cs](MyApp/Program.cs#L41))
 - Hot Module Replacement (HMR) enabled via WebSocket proxying using `MapNotFoundToNode`, `MapNextHmr`, `RunNodeProcess`, `MapFallbackToNode` in [Program.cs](MyApp/Program.cs)
 
@@ -417,7 +417,7 @@ AutoQuery also matches on pluralized fields where `Ids` matches `Id` and applies
 const api = client.api(new QueryBookings({ ids:[1,2,3] }))
 ```
 
-Multiple Request DTO properties applies mutliple **AND** filters, e.g:
+Multiple Request DTO properties applies multiple **AND** filters, e.g:
 
 ```typescript
 const api = client.api(new QueryBookings({ minCost:100, ids:[1,2,3] }))
@@ -493,7 +493,7 @@ The `api` and `apiVoid` APIs return an `ApiResult<Response>` which holds both su
 ```typescript
 const api = await client.api(new Hello({ name }))
 if (api.succeeded) {
-    console.log(`The API succeded:`, api.response)
+    console.log(`The API succeeded:`, api.response)
 } else if (api.error) {
     console.log(`The API failed:`, api.error)
 }
@@ -506,7 +506,7 @@ const submit = async (e: React.FormEvent) => {
     const form = e.currentTarget as HTMLFormElement
     const api = await client.apiForm(new CreateContact(), new FormData(form))
     if (api.succeeded) {
-        console.log(`The API succeded:`, api.response)
+        console.log(`The API succeeded:`, api.response)
     } else if (api.error) {
         console.log(`The API failed:`, api.error)
     }
@@ -635,7 +635,7 @@ Configured in [Configure.BackgroundJobs.cs](MyApp/Configure.BackgroundJobs.cs) u
    - `npx okai Feature.d.ts`
    - `npm run migrate`
 
-Docs: [AutoQuery Dev Worfklow](https://react-templates.net/docs/autoquery/dev-workflow)
+Docs: [AutoQuery Dev Workflow](https://react-templates.net/docs/autoquery/dev-workflow)
 
 ## Admin Features
 

content/docs/configuration.mdx

@@ -45,7 +45,7 @@ services.AddSingleton<IEmailSender<ApplicationUser>, EmailSender>();
 
 ### App Settings Secrets
 
-Instead of polluting each GitHub Reposity with multiple App-specific GitHub Action Secrets, you can save all your secrets in a single `APPSETTINGS_PATCH` GitHub Action Secret to patch `appsettings.json` with environment-specific configuration using [JSON Patch](https://jsonpatch.com). E.g:
+Instead of polluting each GitHub Repository with multiple App-specific GitHub Action Secrets, you can save all your secrets in a single `APPSETTINGS_PATCH` GitHub Action Secret to patch `appsettings.json` with environment-specific configuration using [JSON Patch](https://jsonpatch.com). E.g:
 
 ```json
 [
@@ -55,8 +55,8 @@ Instead of polluting each GitHub Reposity with multiple App-specific GitHub Acti
         "value":"Server=service-postgres;Port=5432;User Id=dbuser;Password=dbpass;Database=dbname;Pooling=true;"
     },
     { "op":"add", "path":"/SmtpConfig", "value":{
-        "UserName": "SmptUser",
-        "Password": "SmptPass",
+        "UserName": "SmtpUser",
+        "Password": "SmtpPass",
         "Host": "email-smtp.us-east-1.amazonaws.com",
         "Port": 587,
         "From": "noreply@example.org",
@@ -95,8 +95,8 @@ npx add-in db-identity
 
 ### App Settings Secrets
 
-You could register any App-specifc secrets here, although our preference is instead of polluting each 
-GitHub Reposity with multiple App-specific GitHub Action Secrets, you can save all your secrets in a single 
+You could register any App-specific secrets here, although our preference is instead of polluting each 
+GitHub Repository with multiple App-specific GitHub Action Secrets, you can save all your secrets in a single 
 `APPSETTINGS_PATCH` GitHub Action Secret to patch `appsettings.json` with environment-specific configuration 
 using [JSON Patch](https://jsonpatch.com). E.g:
 
@@ -115,8 +115,8 @@ JSON Patch example:
         "value":"Server=service-postgres;Port=5432;User Id=dbuser;Password=dbpass;Database=dbname"
     },
     { "op":"add", "path":"/SmtpConfig", "value":{
-        "UserName": "SmptUser",
-        "Password": "SmptPass",
+        "UserName": "SmtpUser",
+        "Password": "SmtpPass",
         "Host": "email-smtp.us-east-1.amazonaws.com",
         "Port": 587,
         "From": "noreply@example.org",

content/docs/deployments.mdx

@@ -57,8 +57,8 @@ The only secret that needs to be configured per App is:
 gh secret set KAMAL_DEPLOY_HOST <www.example.org>
 ```
 
-You could register any App-specifc secrets here, although our preference is instead of polluting each 
-GitHub Reposity with multiple App-specific GitHub Action Secrets, you can save all your secrets in a single 
+You could register any App-specific secrets here, although our preference is instead of polluting each 
+GitHub Repository with multiple App-specific GitHub Action Secrets, you can save all your secrets in a single 
 `APPSETTINGS_PATCH` GitHub Action Secret to patch `appsettings.json` with environment-specific configuration 
 using [JSON Patch](https://jsonpatch.com). E.g:
 
@@ -77,8 +77,8 @@ JSON Patch example:
         "value":"Server=service-postgres;Port=5432;User Id=dbuser;Password=dbpass;Database=dbname"
     },
     { "op":"add", "path":"/SmtpConfig", "value":{
-        "UserName": "SmptUser",
-        "Password": "SmptPass",
+        "UserName": "SmtpUser",
+        "Password": "SmtpPass",
         "Host": "email-smtp.us-east-1.amazonaws.com",
         "Port": 587,
         "From": "noreply@example.org",

content/docs/index.mdx

@@ -129,7 +129,7 @@ very likely to become the future of software development, especially for UIs. Si
 the primary authors of code, our UI choices swing from Developer preferences to UI technologies that AI models
 excel at.
 
-So whilst we have a preference for Vue given it's more readable syntax and progressive enhancement capabalities, and despite the .NET ecosystem having a strong bias towards Blazor, we're even more excited for the future of React and are committed to providing the best possible support for it.
+So whilst we have a preference for Vue given it's more readable syntax and progressive enhancement capabilities, and despite the .NET ecosystem having a strong bias towards Blazor, we're even more excited for the future of React and are committed to providing the best possible support for it.
 
 
 **Vibe Coding** is a new paradigm for building web applications, combining the best-in-class technologies for a developer experience that feels like magic.

content/docs/vibe-coding/budget-planner.mdx

@@ -50,7 +50,7 @@ Reports
 
 The generated source code for the App was uploaded to: [github.com/mythz/budgets.apps.cafe](https://github.com/mythz/budgets.apps.cafe)
 
-### Budgent Planner App
+### Budget Planner App
 
 After a few minutes Copilot creates a PR with what we asked for, even things that we didn't specify in the prompt but could be inferred from the Project Template like **Dark Mode** support where it made use of the existing `<DarkModeToggle />`.
 

content/docs/vibe-coding/rewrite-legacy-uis.mdx

@@ -128,11 +128,11 @@ Implement the NEXTJS_MIGRATION_PLAN.md
 
 With access to both the Migration Plan and existing code-base, Claude Code was able to generate the entire new Next.js UI within 10-20 minutes, for less than $10 (in free credits).
 
-The initial AI-generated code wasn't perfect, but it generated an excellent starting point that converted most of the existing Nust/Vuetify implementation into a modern Next.js App, with its preferred project structure.
+The initial AI-generated code wasn't perfect, but it generated an excellent starting point that converted most of the existing Nuxt/Vuetify implementation into a modern Next.js App, with its preferred project structure.
 
 ### Vibe Code the rest
 
-The most time consuming part of the mgiration is walking through the entire Application, in tandem with your existing App to test that everything functions as it did before. Fortunately you never need to take the reins to get it over the line,
+The most time consuming part of the migration is walking through the entire Application, in tandem with your existing App to test that everything functions as it did before. Fortunately you never need to take the reins to get it over the line,
 as now that we have a modern AI-friendly Next.js/React/Tailwind UI we can just use Vibe Coding to prompt the AI Models to implement any missing features or fix any issues that you find along the way.
 
 If this is your first time using AI Models for all development, it can seem like unrealistic magic from the future.