Address ALL PR comments

Author: nenharper

docs/getting-started/first-harper-app.md

@@ -39,27 +39,36 @@ Harper automatically creates your Book table and REST endpoints. You now have a
 
 ## Test Your API
 ### Create a book:
-```bash
-curl -X POST -H "Content-Type: application/json" \
-  -d '{"title": "The Great Gatsby", "author": "F. Scott Fitzgerald", "publishedYear": 1925, "genre": "Fiction"}' \
-  http://localhost:9926/Book
+```javascript
+const response = await fetch('http://localhost:9926/Book', {
+  method: 'POST',
+  headers: { 'Content-Type': 'application/json' },
+  body: JSON.stringify({
+    title: "The Great Gatsby",
+    author: "F. Scott Fitzgerald", 
+    publishedYear: 1925,
+    genre: "Fiction"
+  })
+});
+const newBook = await response.json();
 ```
 
 ### Get all books:
-```bash
-curl http://localhost:9926/Book
+```javascript
+const books = await fetch('http://localhost:9926/Book').then(r => r.json());
 ```
 
 ### Query by indexed fields:
-```bash
-curl "http://localhost:9926/Book?author=F. Scott Fitzgerald"
-curl "http://localhost:9926/Book?genre=Fiction"
-curl "http://localhost:9926/Book?publishedYear=1925&select(title,author)"
+```javascript
+const authorBooks = await fetch('http://localhost:9926/Book?author=Chimamanda')
+  .then(r => r.json());
+const fictionTitles = await fetch('http://localhost:9926/Book?genre=Fiction&select(title,author)')
+  .then(r => r.json());
 ```
 
 ### Get a specific book:
 ```bash
-curl http://localhost:9926/Book/BOOK_ID_HERE
+const book = await fetch(`http://localhost:9926/Book/${bookId}`).then(r => r.json());
 ```
 
 ## What You Get Automatically
@@ -73,11 +82,11 @@ Harper provides enterprise-grade features out of the box:
 - **Error handling** and proper HTTP status codes
 
 ## Add Custom Logic (Optional)
-Only when you need custom business logic should you add code. Create a `resources.js` file to extend the default behavior:
+Only when you need custom business logic should you add code. Create a `resources.js` file to define a new resource and add custom functionality:
 
 ```js
 export class Books extends Resource {
-  // Add custom validation or computed fields
+  const { Book } = tables;
   post(data) {
     if (!data.title || !data.author) {
       return { error: "Title and author are required" };
@@ -88,7 +97,7 @@ export class Books extends Resource {
       data.decade = Math.floor(data.publishedYear / 10) * 10;
     }
 
-    return this.table.post(data);
+    return Book.post(data);
   }
 }
 ```

docs/getting-started/harper-concepts.md

@@ -8,7 +8,7 @@ Harper components are a core Harper concept defined as flexible JavaScript based
 A key aspect to components are their extensibility; components can be built on other components. For example, a [Harper Application](https://docs.harperdb.io/docs/developers/applications) is a component that uses many other components. The [application template](https://github.com/HarperDB/application-template) demonstrates many of Harper's built-in components such as [rest](https://docs.harperdb.io/docs/developers/components/built-in#rest) (for automatic REST endpoint generation), graphqlSchema (for table schema definitions), and many more.
 
 ## Applications
-Applications are a subset of components that cannot be used directly and must depend on other extensions. Examples include defining schemas (using [graphqlSchema](https://docs.harperdb.io/docs/developers/components/built-in#graphqlschema) built-in extension), defining custom resources (using jsResource built-in extension), hosting static files (using static built-in extension), enabling REST querying of resources (using rest built-in extension), and running Next.js, Astro, or Apollo applications through their respective extensions.
+Applications are a subset of components that cannot be used directly and must depend on other extensions. Examples include defining schemas (using [graphqlSchema](https://docs.harperdb.io/docs/developers/components/built-in#graphqlschema) built-in extension), defining custom resources (using [jsResource](https://docs.harperdb.io/docs/developers/components/built-in#jsresource) built-in extension), hosting static files (using [static](https://docs.harperdb.io/docs/developers/components/built-in#static) built-in extension), enabling REST querying of resources (using [rest](https://docs.harperdb.io/docs/developers/components/built-in#rest) built-in extension), and running [Next.js](https://github.com/HarperDB/nextjs), [Astro](https://github.com/HarperDB/astro), or [Apollo](https://github.com/HarperDB/apollo) applications through their respective extensions.
 
 ## Resources
 Resources in Harper encompass databases, tables, and schemas that store and structure data within the system. The concept is central to Harper's data management capabilities, with custom resources being enabled by the built-in jsResource extension. Resources represent the data layer of the Harper ecosystem and provide the foundation for data operations across applications built with the platform.

docs/getting-started/install-harper.md

@@ -1,6 +1,6 @@
 # Install Harper
 
-There are three ways to install a Harper instance: using a package manager like NPM, deploying it as a Docker container, and offline installation. Below is a step-by-step tutorial for each method.
+There are three ways to install a Harper instance: using a package manager like npm, deploying it as a Docker container, and offline installation. Below is a step-by-step tutorial for each method.
 
 ## Installing via NPM
 Before you begin, ensure you have [Node.js](https://nodejs.org/) LTS version or newer. Node.js comes with npm, which will be used to install Harper.