Remove outdated part about schema

Author: cahofmeyr

usage/tools/cloudcode.mdx

@@ -184,29 +184,27 @@ The body of the request payload should look like this:
 }
 ```
 
-The `op` refers to the type of operation recorded by the PowerSync client SDK (`PUT`, `PATCH` or `DELETE`). Refer to [Writing Client Changes](/installation/app-backend-setup/writing-client-changes) for details.
+  * `batch` should be an array of operations from the PowerSync client SDK.
+  * `op` refers to the type of each operation recorded by the PowerSync client SDK (`PUT`, `PATCH` or `DELETE`). Refer to [Writing Client Changes](/installation/app-backend-setup/writing-client-changes) for details.
 
 The API will respond with HTTP status `200` if the write was successful.
 
 
-## Customization required
+## Customization 
 
-You can make changes to the way the `upload` task writes data to the source MongoDB database. At a minimum, at this time you will need to modify it to take your specific MongoDB database "schema" into consideration (Note: We are working on updating the template to not require adapting it to your schema. We will update this documentation page accordingly once that change is shipped).
+You can make changes to the way the `upload` task writes data to the source MongoDB database. 
 
 Here is how:
 
-1. Open the **CloudCode** section at the top of the IDE.
+1. Go to **CloudCode** at the top of the IDE in your JourneyApps Platform project
 2. Select and expand the `upload` task in the panel on the left.
-3. The `index.ts` contains the entry point function that accepts the HTTP request and has a `MongoDBStorage` class which interacts with the MongoDB database to perform inserts, updates and deletes. To adjust how updates are performed take a look at the `updateBatch` function.
+3. The `index.ts` contains the entry point function that accepts the HTTP request and has a `MongoDBStorage` class which interacts with the MongoDB database to perform inserts, updates and deletes. To adjust how updates are performed, take a look at the `updateBatch` function.
 
 ## Production considerations
 
 Before going into production with this solution, you will need to set up authentication on the HTTP endpoints exposed by the CloudCode tasks.
 
-If you need more data validations and/or authorization than what is provided by the template, that will need to be customized too.
+If you need more data validations and/or authorization than what is provided by the template, that will need to be customized too. Consider introducing schema validation of the data being written to the source MongoDB database. You should use a [purpose-built](https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=&environments=&showObsolete=false) library for this, and use [MongoDB Schema Validation](https://www.mongodb.com/docs/manual/core/schema-validation/) to enforce the types in the database.
 
-For production applications you would also want to consider introducing schema validation of the data being written to the source MongoDB database.
-You should use a [purpose-built](https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=&environments=&showObsolete=false) library for this, and use MongoDB Schema Validation to enforce the types in the database.
-
-Please [contact us](/resources/contact-us) for assistance on either of the above.
+Please [contact us](/resources/contact-us) for assistance on any of the above.