Fix typos and improve clarity in documentation and code comments across various files. Update CLI command references and enhance error handling in template category management. Ensure consistent formatting in layout components and improve accessibility attributes.

Author: eluce2

apps/docs/content/docs/better-auth/installation.mdx

@@ -18,10 +18,10 @@ This package is currently in beta. Please report any issues you find to the [Git
 
 # Step 1a: Automated Setup with the ProofKit CLI
 <Callout type="warning">
-This automated setup expects you to have Next.js and shadcn/ui setup in your project. It will also setup various auth pages for you, but these may not work if you have a prefix configured for tailwindcss. You can use this opinionated setup to get you started, or if you need more control you should refer to the manual setup.
+This automated setup expects you to have Next.js and shadcn/ui set up in your project. It will also setup various auth pages for you, but these may not work if you have a prefix configured for tailwindcss. You can use this opinionated setup to get you started, or if you need more control you should refer to the manual setup.
 </Callout>
 
-Run the following command to add the neccesary packages and config files to your project. You will not need to follow the better-auth installation guide.
+Run the following command to add the necessary packages and config files to your project. You will not need to follow the better-auth installation guide.
 <CliCommand command="add better-auth" exec />
 
 # Step 1b: Manual Setup
@@ -64,7 +64,7 @@ export const auth = betterAuth({
 Run the following command to create the necessary tables and fields in your FileMaker file. It will show you a confirmation before any changes are applied, so you can review them.
 <CliCommand command="migrate" exec execPackage="@proofkit/better-auth@latest" />
 
-[Full Access] credentials are required for the schema changes to be applied automatically, but you may want to use a more restricted account for the rest of better-auth usage. If your credentials that you entered eariler in the `auth.ts` file do not have the [Full Access] permissions, you can override them in the CLI.
+[Full Access] credentials are required for the schema changes to be applied automatically, but you may want to use a more restricted account for the rest of better-auth usage. If your credentials that you entered earlier in the `auth.ts` file do not have the [Full Access] permissions, you can override them in the CLI.
 <CliCommand command={`migrate --username "full_access_username" --password "full_access_password"`} exec execPackage="@proofkit/better-auth@latest" />
 
 These changes affect database schema only. No layouts or relationships are created or modified during this process.

apps/docs/content/docs/cli/guides/adding-components/index.mdx

@@ -7,7 +7,7 @@ icon: puzzle
 import { CliCommand } from "@/components/CliCommand";
 
 
-After initilizing a new ProofKit project, you can use the CLI to add new components and features.
+After initializing a new ProofKit project, you can use the CLI to add new components and features.
 
 <Callout title="Major changes in v2!">
 The `add` is now more dynamic and may change over time. To see all available items you can add via this command, see the [full list of templates available here](/docs/templates)

apps/docs/content/docs/cli/guides/auth/add-on.mdx

@@ -7,7 +7,7 @@ import { CliCommand } from "@/components/CliCommand";
 
 
 <Callout type="warning" title="Deprecated">
-This component is no longer the reccomended approach for self-hosting your web app's authentication in FileMaker. Instead, check out the [Better-Auth installation guide](/docs/better-auth/installation) for a more flexible and customizable solution.
+This component is no longer the recommended approach for self-hosting your web app's authentication in FileMaker. Instead, check out the [Better-Auth installation guide](/docs/better-auth/installation) for a more flexible and customizable solution.
 </Callout>
 
 ProofKit includes a self-hosted authentication solution that is built to be flexible and easy to customize. Rather than using a third-party library or authentication service, the ProofKit CLI installs all of the necessary functions into your project and then you just have to install the FileMaker add-on in your FileMaker file to get the necessary tables in your database.

apps/docs/content/docs/cli/guides/motivation.mdx

@@ -72,4 +72,4 @@ A hosted authentication service that is extremely easy to set up and use. It's a
 
 #### [Better-Auth](https://better-auth.com/) (self-hosted)
 
-For when you need a bit more flexibility or if you want to self-host the authentication layer within your existing FileMaker solution. Better-auth is a great choice for this, and the [proofkit/better-auth](/docs/better-auth) adapter allows you to use FileMaker as your backend database, including automated schema migrations to easily add any neccesary tables and fields to your FileMaker file.
+For when you need a bit more flexibility or if you want to self-host the authentication layer within your existing FileMaker solution. Better-auth is a great choice for this, and the [proofkit/better-auth](/docs/better-auth) adapter allows you to use FileMaker as your backend database, including automated schema migrations to easily add any necessary tables and fields to your FileMaker file.

apps/docs/content/docs/cli/index.mdx

@@ -10,15 +10,13 @@ import { Card } from "fumadocs-ui/components/card";
 ## What is ProofKit?
 ProofKit is a collection of TypeScript tools and libraries for building modern web applications, with a focus on seamless integration with Claris FileMaker.
 
-The ProofKit CLI aims to make web development easier for beginners and more efficient for experienced devs. It’s opinionated structure allows for more than just a starter template or bootstrapping tool, but code-mod scripts that can modify a project after the initial setup.
+The ProofKit CLI aims to make web development easier for beginners and more efficient for experienced devs. Its opinionated structure allows for more than just a starter template or bootstrapping tool, but code-mod scripts that can modify a project after the initial setup.
 
 Think of it as our experience building web apps encapsulated into a CLI tool to help you structure your project and add to it over time. Each template is just a starting point, and you are free to modify any part of it as you see fit.
 
 ## Core Libraries
 
-The ProofKit CLI will automatically install these other packages for you (depending on what you choose to build), but they are published seperately if you want to use them in your own projects, without the opinionated structure provided by the CLI.
-
-
+The ProofKit CLI will automatically install these other packages for you (depending on what you choose to build), but they are published separately if you want to use them in your own projects, without the opinionated structure provided by the CLI.
 <Cards>
   <Card href="/docs/fmdapi" title="@proofkit/fmdapi">
 A library for interacting with the FileMaker Data API.

apps/docs/content/docs/cli/v2.mdx

@@ -7,19 +7,19 @@ description: In this major release, the ProofKit CLI has been reimagined as a mo
 
 ### A new starting point
 
-When you start a new app using the ProofKit CLI, the new template is based on shadcn and tailwindcss instead of Mantine. This new simple template still includes the best practices from the Proof+Geist team, but with now with even more flexibility.
+When you start a new app using the ProofKit CLI, the new template is based on shadcn and tailwindcss instead of Mantine. This new simple template still includes the best practices from the Proof+Geist team, but now with even more flexibility.
 
 ### A new way to add [anything]
 
 The `proofkit add` command leverages the shadcn CLI to install any component or utility into your app, or you can use the shadcn CLI directly to install any component from any compatible library. Even better, these templates are now published right here on the docs site, so we can more easily release updates and new components that you can use right away.
 
 ### A new level of compatibility
 
-You can now use the ProofKit CLI in an existing Next.js app, even if it wasn’t bootstraped with the CLI, as long as it's already using shadcn. This unlocks the ability for more advanced developers to leverage the power of ProofKit, while still trying out the latest and greatest in the JavaScript ecosystem.
+You can now use the ProofKit CLI in an existing Next.js app, even if it wasn’t bootstrapped with the CLI, as long as it's already using shadcn. This unlocks the ability for more advanced developers to leverage the power of ProofKit, while still trying out the latest and greatest in the JavaScript ecosystem.
 
 # Why the change?
 
-Adding new templates to the ProofKit CLI was always a challenge, and arugably the most lacking of the whole system. The templates are meant to be just a starting place, so they needed to be generic to fit any project, yet useful enough to warrant inclusion in the binary everyone downloads to run the CLI. That wasn’t scalable. But shadcn has taken the JavaScript world by storm of the past few year, especially with the rise of AI and especially tools like v0. We needed to unlock the ability to easily add anything to your JavaScript projects, whether it was a template from Proof, shadcn, v0 (AI-generated), or from any of the other emerging UI libraries built on the shadcn CLI.
+Adding new templates to the ProofKit CLI was always a challenge, and arguably the most lacking of the whole system. The templates are meant to be just a starting place, so they needed to be generic to fit any project, yet useful enough to warrant inclusion in the binary everyone downloads to run the CLI. That wasn’t scalable. But shadcn has taken the JavaScript world by storm over the past few years, especially with the rise of AI and especially tools like v0. We needed to unlock the ability to easily add anything to your JavaScript projects, whether it was a template from Proof, shadcn, v0 (AI-generated), or from any of the other emerging UI libraries built on the shadcn CLI.
 
 But this required a new starting point. While mantine and tailwind can be used together in the same project, they get in each other’s way. At Proof+Geist, we’ve been building new projects without ProofKit for a few months now, so it was time to bring those learnings back to the framework so we could all move more quickly. New projects will start with a new foundation based on tailwindcss. It’s easier for AI to understand, and more compatible with any UI component built for shadcn to install for you.
 

apps/docs/src/app/docs/templates/category-config.ts

@@ -49,5 +49,9 @@ export const categoryConfigMap = categoryConfigs.reduce(
 
 // Helper function to get category configuration
 export const getCategoryConfig = (category: Category): CategoryConfig => {
-  return categoryConfigMap[category];
+  const config = categoryConfigMap[category];
+  if (!config) {
+    throw new Error(`Unknown template category: ${category as string}`);
+  }
+  return config;
 };

apps/docs/src/app/docs/templates/layout.tsx

@@ -88,6 +88,7 @@ export default async function Layout({ children }: { children: ReactNode }) {
               <a
                 href="https://proofgeist.com"
                 target="_blank"
+                rel="noopener noreferrer"
                 className="underline"
               >
                 Proof+Geist

apps/docs/src/app/docs/templates/templates-client.tsx

@@ -4,19 +4,28 @@ import { useState, useMemo } from "react";
 import Link from "next/link";
 import { Search, Package } from "lucide-react";
 import type { TemplateWithPath } from "@/lib/templates";
-import { getCategoryConfig, categoryConfigs } from "./category-config";
+import {
+  getCategoryConfig,
+  categoryConfigs,
+  type CategoryConfig,
+} from "./category-config";
+import type { TemplateMetadata } from "@proofkit/registry";
+
+type Category = TemplateMetadata["category"];
 
 interface TemplatesPageClientProps {
   templates: TemplateWithPath[];
-  templatesByCategory: Record<string, TemplateWithPath[]>;
+  templatesByCategory: Record<Category, TemplateWithPath[]>;
 }
 
 export function TemplatesPageClient({
   templates,
   templatesByCategory,
 }: TemplatesPageClientProps) {
   const [searchQuery, setSearchQuery] = useState("");
-  const [selectedCategory, setSelectedCategory] = useState<string | null>(null);
+  const [selectedCategory, setSelectedCategory] = useState<Category | null>(
+    null,
+  );
 
   const filteredTemplates = useMemo(() => {
     let filtered = templates;
@@ -79,7 +88,7 @@ export function TemplatesPageClient({
             All ({templates.length})
           </button>
           {categories.map((category) => {
-            const config = getCategoryConfig(category as any);
+            const config = getCategoryConfig(category);
             const CategoryIcon = config.icon;
             return (
               <button
@@ -111,7 +120,7 @@ export function TemplatesPageClient({
                 {" "}
                 in{" "}
                 <span className="font-medium">
-                  {getCategoryConfig(selectedCategory as any).name}
+                  {getCategoryConfig(selectedCategory).name}
                 </span>
               </span>
             )}
@@ -137,7 +146,7 @@ export function TemplatesPageClient({
                   <div className="shrink-0 mt-1">
                     {(() => {
                       const CategoryIcon = getCategoryConfig(
-                        template.category as any,
+                        template.category,
                       ).icon;
                       return <CategoryIcon className="h-5 w-5 text-primary" />;
                     })()}

apps/docs/src/components/CliCommand.tsx

@@ -20,7 +20,7 @@ const MANAGERS = [
     key: "yarn",
     label: "yarn",
     prefix: "yarn",
-    execPrefix: "npx",
+    execPrefix: "yarn dlx",
   },
   {
     key: "bun",