diff --git a/client-sdk-references/dotnet.mdx b/client-sdk-references/dotnet.mdx
index 2e89d61b..6e25ca96 100644
--- a/client-sdk-references/dotnet.mdx
+++ b/client-sdk-references/dotnet.mdx
@@ -19,9 +19,9 @@ import DotNetInstallation from '/snippets/dotnet/installation.mdx';
     A full API Reference for this SDK is not yet available. This is planned for a future release.
   </Card>
 
-  <Card title="Example App" icon="code" href="https://github.com/powersync-ja/powersync-dotnet/tree/main/demos/CommandLine">
-    A small CLI app showcasing bidirectional sync.
-  </Card>
+    <Card title="Example Projects" icon="code" href="/resources/demo-apps-example-projects#net-alpha">
+        Gallery of example projects/demo apps built with .NET and PowerSync.
+    </Card>
 </CardGroup>
 
 <Warning>
diff --git a/installation/app-backend-setup/writing-client-changes.mdx b/installation/app-backend-setup/writing-client-changes.mdx
index 9e6babad..d798056a 100644
--- a/installation/app-backend-setup/writing-client-changes.mdx
+++ b/installation/app-backend-setup/writing-client-changes.mdx
@@ -49,6 +49,10 @@ We do however recommend the following:
     1. Including the error details in the `2xx` response.
     2. Writing the error(s) into a separate table/collection that is synced to the client, so that the client/user can handle the error(s).
 
+<Note>
+If you don't call `.complete()` on an operation, it will remain in the queue and continue to be retried. This may be intentional to maintain consistency with your remote database, but be aware that incomplete operations will prevent the queue from progressing past that point.
+</Note>
+
 For details on approaches, see:
 
 <CardGroup>
diff --git a/self-hosting/installation/powersync-service-setup.mdx b/self-hosting/installation/powersync-service-setup.mdx
index 74b0c391..8306f274 100644
--- a/self-hosting/installation/powersync-service-setup.mdx
+++ b/self-hosting/installation/powersync-service-setup.mdx
@@ -160,7 +160,7 @@ client_auth:
   # supabase_jwt_secret: your-secret
 
   # JWKS URIs can be specified here.
-  jwks_uri: http://demo-backend:6060/api/auth/keys
+  jwks_uri: http://demo-backend:6060/api/auth/keys # Not applicable for Supabase
 
   # JWKS audience
   audience: ['powersync-dev', 'powersync']
diff --git a/tutorials/self-host/generate-dev-token.mdx b/tutorials/self-host/generate-dev-token.mdx
index ce0b5a1a..005085c9 100644
--- a/tutorials/self-host/generate-dev-token.mdx
+++ b/tutorials/self-host/generate-dev-token.mdx
@@ -41,7 +41,7 @@ Development tokens can be generated via either
         # Client (application end user) authentication settings
         client_auth:
             # JWKS URIs can be specified here
-            jwks_uri: !env PS_JWKS_URL
+            jwks_uri: !env PS_JWKS_URL # Not applicable for Supabase
             jwks:
                 keys:
                     - kty: 'oct'
diff --git a/usage/sync-rules/guide-many-to-many-and-join-tables.mdx b/usage/sync-rules/guide-many-to-many-and-join-tables.mdx
index 869b98cb..b31174a0 100644
--- a/usage/sync-rules/guide-many-to-many-and-join-tables.mdx
+++ b/usage/sync-rules/guide-many-to-many-and-join-tables.mdx
@@ -106,7 +106,7 @@ JOIN posts ON posts.id = comments.post_id
 WHERE board_id = bucket.board_id
 ```
 
-Unfortunately, joins are not supported in PowerSync's Sync Rules. Instead, we denormalize the data to add a direct foreign key relationship between comments and boards: (Postgres example)
+Unfortunately, [JOINS](/usage/sync-rules/parameter-queries#restrictions) are not supported in PowerSync's Sync Rules. Instead, we denormalize the data to add a direct foreign key relationship between comments and boards: (Postgres example)
 
 ```sql
 ALTER TABLE comments ADD COLUMN board_id uuid;