docs: fixed some typos, formatting, grammar (#11540)

# Which Problems Are Solved

- Typos
- Punctuation
- Markdown table formatting
- ...

(A bunch of issues my editor gave)

# How the Problems Are Solved


# Additional Changes


# Additional Context

apps/docs/components/PermissionTable/index.jsx

@@ -1,9 +1,9 @@
 import React, { useMemo } from 'react';
 import yaml from 'js-yaml';
 import { Check, X } from 'lucide-react';
-import { cn } from '@/utils/cn'; // Assuming utils/cn exists or I'll use clsx/tailwind-merge directly if not sure
+import { cn } from '@/utils/cn'; // Assuming utils/cn exists, or I'll use clsx/tailwind-merge directly if not sure
 
-// Fallback utility if generic cn doesn't exist, checking imports first is safer but I'll inline a simple merge if needed
+// Fallback utility if generic cn doesn't exist, checking imports first is safer, but I'll inline a simple merge if needed
 // Checking package.json I saw clsx and tailwind-merge are dependencies.
 
 function classNames(...classes) {

apps/docs/components/version-selector.tsx

@@ -20,7 +20,7 @@ export function VersionSelector() {
 
     // Handle basePath issues: usePathname() typically returns path relative to basePath if configured?
     // But purely relying on that is tricky. Let's normalize.
-    // If pathname starts with /docs, assume it's the full path and we strip it for logic, 
+    // If pathname starts with /docs, assume it's the full path, and we strip it for logic,
     // then let router handle re-adding it if needed (or we check behaviors).
     // Actually, Next.js router.push() expects path relative to basePath usually?
     // Let's implement robust segment swapping.