updates

Author: ymc9

versioned_docs/version-3.x/_components/_zmodel-starter.md

@@ -1,7 +1,7 @@
   ```zmodel
   datasource db {
       provider = 'sqlite'
-      url = "file:./dev.db"
+      url = 'file:./dev.db'
   }
 
   model User {

versioned_docs/version-3.x/migrate-prisma.md

@@ -159,7 +159,7 @@ ZenStack has its own CLI plugin system and doesn't support Prisma custom generat
     }
     ```
 
-2. Run a`prisma generate` command after `zen generate` with the prisma schema as input.
+2. Run a `prisma generate` command after `zen generate` with the prisma schema as input.
    
    ```json
    {
@@ -175,7 +175,7 @@ ZenStack has its own [runtime plugin mechanism](./orm/plugins/) and doesn't plan
 
 **1. Query extension**
 
-[Query extension](https://www.prisma.io/docs/orm/prisma-client/client-extensions/query) allows you to intercepts ORM query calls.
+[Query extension](https://www.prisma.io/docs/orm/prisma-client/client-extensions/query) allows you to intercept ORM query calls.
 
 Suppose you have an extension like:
 
@@ -258,4 +258,4 @@ export const db = new ZenStackClient(schema, {
 });
 ```
 
-The biggest difference is ZenStack's computed fields are evaluated on the database side, which much more efficient and flexible than client-side computation. Read more in the [Computed Fields](./orm/computed-fields.md) documentation.
+A key difference is that ZenStack's computed fields are evaluated on the database side, which much more efficient and flexible than client-side computation. Read more in the [Computed Fields](./orm/computed-fields.md) documentation.

versioned_docs/version-3.x/modeling/index.md

@@ -39,7 +39,7 @@ model Post {
     content   String
     published Boolean  @default(false)
     author    User     @relation(fields: [authorId], references: [id])
-    authorId  String
+    authorId  Int
 }
 ```
 

versioned_docs/version-3.x/modeling/model.md

@@ -21,7 +21,7 @@ model User {
 }
 ```
 
-The simplest models are just a collection of fields. A model must be uniquely identifiable by some of its fields. For most cases, you'll have a field marked with the `@id` attribute (more about [attributes](./attribute) later). 
+The simplest models are just a collection of fields. A model must be uniquely identifiable by some of its fields. In most cases, you'll have a field marked with the `@id` attribute (more about [attributes](./attribute) later). 
 
 ```zmodel
 model User {
@@ -115,7 +115,7 @@ Each model field must at least have a name and a type. A field can be typed in o
     ```
 4. Custom type
    
-   ZenStack allows you to define custom types in the schema and use them to type JSON fields. This will be covered in more detail in the [Custom Type](./custom-type) section.
+   ZenStack allows you to define custom types in the schema and use them to type JSON fields. This is covered in more detail in the [Custom Type](./custom-type) section.
 
    ```zmodel
    type Address {
@@ -144,7 +144,7 @@ model User {
 }
 ```
 
-A default value can be specified for a field with the `@default` attribute. The value can be a literal, or a supported function call, including:
+A default value can be specified for a field with the `@default` attribute. The value can be a literal, an enum value, or a supported function call, including:
 
 - `now()`: returns the current timestamp
 - `cuid()`: returns a CUID
@@ -156,8 +156,8 @@ A default value can be specified for a field with the `@default` attribute. The
 
 ```zmodel
 model User {
-    id        Int  @id @default(autoincrement())
-    role      Role @default("USER")
+    id        Int      @id @default(autoincrement())
+    role      Role     @default(USER)
     createdAt DateTime @default(now())
 }
 ```

versioned_docs/version-3.x/modeling/polymorphism.md

@@ -25,7 +25,7 @@ It may be tempting to use mixins to share the common fields, however it's not an
 - There's no efficient and clean way to query all content types together (e.g., all content owned by a user).
 - Consequently, whenever you add a new content type, you'll need to modify the `User` model, and probably lots of query code too.
 
-A true solution involves having a in-database model of polymorphism, where we really have a `Content` table that serves as an intermediary between `User` and the concrete content types. This is what ZModel polymorphism is about.
+A true solution involves having an in-database model of polymorphism, where we really have a `Content` table that serves as an intermediary between `User` and the concrete content types. This is what ZModel polymorphism is about.
 
 :::info
 There are [two main ways](https://www.prisma.io/docs/orm/prisma-schema/data-model/table-inheritance) to model polymorphism in relational databases: single-table inheritance (STI) and multi-table inheritance (MTI, aka. "Delegate Types"). ZModel only supports MTI.
@@ -99,12 +99,12 @@ erDiagram
     Video ||--|| Content: delegates
 ```
 
-There are two special things about polymorphic base model:
+There are two special things about a polymorphic base model:
 
 1. It must have a "discriminator" field that stores the concrete model type that it should "delegate" to. In the example above, the `type` field serves this purpose. It can be named anything you like, but must be of `String` or enum type.
 2. It must have a `@@delegate` attribute. The attribute serves two purposes: it indicates that the model is a base model, and it designates the discriminator field with its parameter.
 
-You can also have a deep hierarchy involving multiple level of base models. Just need to make sure each base model has its own discriminator field and `@@delegate` attribute. Extending from multiple base models directly is not supported.
+You can also have a deep hierarchy involving multiple levels of base models. Just need to make sure each base model has its own discriminator field and `@@delegate` attribute. Extending from multiple base models directly is not supported.
 
 ## Migration behavior
 

versioned_docs/version-3.x/modeling/relation.md

@@ -5,7 +5,7 @@ description: Relations in ZModel
 
 # Relation
 
-Relation is a fundamental concept in relational databases. It lets you connect models into a graph, and allows you to query interconnected data efficiently. In ZModel, relations are modeled using the `@relation` attribute. For most cases, it involves one side of the relation defining a foreign key field that references the primary key of the other side. By convention, we call the model that holds the foreign key the "owner" side.
+Relations are a fundamental concept in relational databases. They connect models into a graph and allow you to query interconnected data efficiently. In ZModel, relations are modeled using the `@relation` attribute. In most cases, it involves one side of the relation defining a foreign key field that references the primary key of the other side. By convention, we call the model that holds the foreign key the "owner" side.
 
 ## One-to-one relation
 
@@ -272,13 +272,13 @@ enum ReferentialAction {
 
 ```zmodel
 model User {
-    id String @id
+    id String        @id
     profile Profile?
 }
 
 model Profile {
-    id String @id
-    user @relation(fields: [userId], references: [id], onUpdate: Cascade, onDelete: Cascade)
+    id String     @id
+    user User     @relation(fields: [userId], references: [id], onUpdate: Cascade, onDelete: Cascade)
     userId String @unique
 }
 ```

versioned_docs/version-3.x/orm/index.md

@@ -48,7 +48,7 @@ ZenStack ORM comes with a powerful built-in access control system. You can defin
 ```zmodel
 model Post {
     id        Int     @id
-    title     String  @length(1, 256)
+    title     String
     published Boolean @default(false)
     author    User    @relation(fields: [authorId], references: [id])
     authorId  Int
@@ -71,7 +71,7 @@ Real-world applications often involves storing polymorphic data which is notorio
 ```zmodel
 model Content {
     id    Int    @id
-    name  String @length(1, 256)
+    name  String
     type  String
 
     // the ORM uses the `type` field to determine to which concrete model

versioned_docs/version-3.x/reference/zmodel/datasource.md

@@ -17,7 +17,7 @@ datasource NAME {
 
 -   **NAME**:
 
-    Name of the data source. Needs to be a valid identifier matching regular expression `[A-Za-z][a-za-z0-9_]\*`. Name is only informational and serves no other purposes.
+    Name of the data source. Must be a valid identifier. Name is only informational and serves no other purposes.
 
 -   **`provider`**:
 

versioned_docs/version-3.x/reference/zmodel/model.md

@@ -4,7 +4,7 @@ sidebar_position: 2
 
 # Model
 
-Models represent the business entities of your application. A model can have zero or more [mixins](../../modeling/mixin.md), and zero or more [polymorphic base models](../../modeling/polymorphism.md).
+Models represent the business entities of your application. A model can have zero or more [mixins](../../modeling/mixin.md), and zero or one [polymorphic base models](../../modeling/polymorphism.md).
 
 ## Syntax
 
@@ -16,7 +16,7 @@ model NAME (with MIXIN_NAME(,MIXIN_NAME)*)? (extends BASE_NAME)? {
 ```
 -   **NAME**:
 
-    Name of the model. Needs to be unique in the entire schema. Needs to be a valid identifier matching regular expression `[A-Za-z][a-za-z0-9_]\*`.
+    Name of the model. Needs to be unique in the entire schema. Must be a valid identifier.
 
 -   **FIELD**:
 
@@ -36,9 +36,9 @@ model NAME (with MIXIN_NAME(,MIXIN_NAME)*)? (extends BASE_NAME)? {
 
 ## Note
 
-A model must be uniquely identifiable by one or several of its fields. For most cases, you'll have a field marked with the `@id` attribute. If needed, you can use multiple fields as unique identifier by using the `@@id` model-level attribute.
+A model must be uniquely identifiable by one or several of its fields. In most cases, you'll have a field marked with the `@id` attribute. If needed, you can use multiple fields as unique identifier by using the `@@id` model-level attribute.
 
-If no `@id` or `@@id` is specified, field(s) marked with the `@unique` or `@@unique` attribute will be used as fallback identifier.
+If no `@id` or `@@id` is specified, the field(s) marked with the `@unique` or `@@unique` attribute will be used as fallback identifier.
 
 ## Example
 

versioned_docs/version-3.x/reference/zmodel/plugin.md

@@ -17,7 +17,7 @@ plugin PLUGIN_NAME {
 
 -   **PLUGIN_NAME**
 
-    Name of the plugin. Needs to be unique in the entire model. Needs to be a valid identifier matching regular expression `[A-Za-z][a-za-z0-9_]\*`.
+    Name of the plugin. Needs to be unique in the entire model. Must be a valid identifier.
 
 -   **`provider`**