PR feedback

Author: Hein

usage/tools.mdx

@@ -9,5 +9,5 @@ mode: wide
 <Card title="CLI (Beta)" icon="terminal" href="/usage/tools/cli" horizontal/>
 <Card title="Diagnostics App" icon="stethoscope" href="https://github.com/powersync-ja/powersync-js/tree/main/tools/diagnostics-app" horizontal/>
 <Card title="Monitoring and Alerting" icon="bell" href="/usage/tools/monitoring-and-alerting" horizontal/>
-<Card title="MongoDB CRUD Auth Backend" icon="database" href="/usage/tools/mongodb-crud-auth-backend" horizontal/>
+<Card title="MongoDB CRUD & Auth Backend" icon="database" href="/usage/tools/mongodb-crud-auth-backend" horizontal/>
 </CardGroup>

usage/tools/mongodb-crud-auth-backend.mdx

@@ -1,5 +1,5 @@
 ---
-title: MongoDB CRUD Auth Backend
+title: MongoDB CRUD & Auth Backend
 description:
 ---
 
@@ -19,7 +19,10 @@ Here you will find four CloudCode tasks:
 </Frame>
 
 1. `generate_keys` - This is a task that can be used to generate a private/public key pair which the `jwks` and `token` tasks require.
-This task does not expose an HTTP endpoint and should only be used for development and getting started.
+
+<Warning>
+    This task does not expose an HTTP endpoint and should only be used for development and getting started.
+</Warning>
 2. `jwks` - This exposes an HTTP endpoint which has a `GET` function which returns the public JWKS details.
 3. `token` - This task exposes an HTTP endpoint which has a `GET` function. This tasks is used by a PowerSync client to generate a token to validate against the PowerSync Service.
 For more information about custom authentication setups for PowerSync, please see [this page](https://docs.powersync.com/installation/authentication-setup/custom) from the PowerSync docs.