Merge pull request #2654 from mooreds/mooreds/correct-bundle-docs

docs(bundles): corrected grammar and JSON issues in Bundle docs, and updated the example for consistency

Author: tolgaozen

docs/operations/bundle.mdx

@@ -3,50 +3,52 @@ icon: cube
 title: Data Bundles
 ---
 
-## What is Data Bundles
+## What are Data Bundles
 
 Ensuring that authorization data remains in sync with the business model is an important practice when using Permify.
 
 Prior to Data Bundles, it was the responsibility of the services (such as [WriteData](../api-reference/data/write-data) API) to structure how relations are created and deleted when actions occur on resources.
 
-With the Data Bundles, you be able to bundle and model the creation and deletion of relations and attributes when specific actions occur on resources in your applications.
+With the Data Bundles, you can model the creation and deletion of relations and attributes when specific actions occur on resources in your applications.
 
-We believe this functionality will streamline managing authorization data as well as managing this in a central place increase visibility around certain actions/triggers that end up with data creation.
+This functionality streamlines managing authorization data, allows you to manage it in a central place, and increases visibility around certain actions/triggers that create data.
 
-## How Bundles Works
+## How Bundles Work
 
-Let's examine how Bundles operates with basic example.
+Let's examine how Bundles operate.
 
-Let's say you want to model how data will be created when an organization created in your application. For this purpose, you can utilize the [WriteBundle](../../api-reference/bundle/write-bundle) API endpoint. This API enables users to define or update data bundles, each distinguished by a unique name.
+Let's say you want to model how data will be created when an organization is created in your application. For this purpose, you can utilize the [WriteBundle](../../api-reference/bundle/write-bundle) API endpoint. This API enables users to define or update data bundles, each distinguished by a unique name.
 
 Here's an example body for WriteBundle in this scenario:
 
 ```json
-"bundles": [
-    {
-        "name": "organization_created"
-        "arguments": [
-            "creatorID",
-            "organizationID"
-        ],
-        "operations": [
-            {
-                "relationships_write": [
-                    "organization:{{.organizationID}}#admin@user:{{.creatorID}}",
-                    "organization:{{.organizationID}}#manager@user:{{.creatorID}}",
-                ],
-                "attributes_write": [
-                    "organization:{{.organizationID}}$public|boolean:false",
-                ],
-            },
-        ],
-    },
-],
+{ 
+    "bundles": [
+        {
+            "name": "organization_created",
+            "arguments": [
+                "creatorID",
+                "organizationID"
+            ],
+            "operations": [
+                {
+                    "relationships_write": [
+                        "organization:{{.organizationID}}#admin@user:{{.creatorID}}",
+                        "organization:{{.organizationID}}#manager@user:{{.creatorID}}"
+                    ],
+                    "attributes_write": [
+                        "organization:{{.organizationID}}$public|boolean:false"
+                    ]
+                }
+            ]
+        }
+    ]
+}
 ```
 
 Operations represent actions that can be performed on relationships and attributes, such as adding or deleting relationships when certain events occur.
 
-Let's say user:564 creates an organization:789 in your application. According to your authorization logic, this will result in the creation of several authorization data, including relational tuples and attributes, respectively.
+Let's say user:564 creates an organization:789 in your application. According to your authorization logic, this will result in the creation of several pieces of authorization data, including relational tuples and attributes:
 
 - organization:789#admin@user:564
 - organization:789#manager@user:564
@@ -57,13 +59,11 @@ Instead of using the [WriteData](../../api-reference/data/write-data) endpoint,
 An example request of [RunBundle](../../api-reference/data/run-bundle) for this scenario:
 
 ```json
-POST /bundle
-BODY
 {
-   "name": "project_created",
+   "name": "organization_created",
    "arguments": {
        "creatorID": "564",
-       "organizationID": "789",
+       "organizationID": "789"
     }
 }
 ```