Fixes (#133)

Author: benitav

images/integration-guides/supabase/diagram-docs-supabase-integration.png

@@ -33,12 +33,12 @@ For web apps, this guide assumes that you have [pnpm](https://pnpm.io/installati
 
 Upon successful integration of Supabase + PowerSync, your system architecture will look like this: (click to enlarge image)
 <Frame>
-  <img src="/images/integration-1.png"/>
+  <img src="/images/integration-guides/supabase/diagram-docs-supabase-integration.png"/>
 </Frame>
 The local SQLite database embedded in the PowerSync SDK is automatically kept in sync with the Supabase Postgres database (based on configured sync rules as you will see later in this guide). Client-side data modifications are persisted in the local SQLite database as well as stored in an upload queue that gets processed via the Supabase client library when network connectivity is available. Therefore reads and writes can happen in the app regardless of whether the user is online or offline, by using the local SQLite database.
 
 <Info>
-  For more details on PowerSync's general architecture, [see here](/architecture/architecture-overview.mdx).
+  For more details on PowerSync's general architecture, [see here](/architecture/architecture-overview).
 </Info>
 
 ## Integration Guide/Tutorial Overview

integration-guides/supabase-+-powersync.mdx

@@ -41,7 +41,7 @@ mode: wide
     **Right now, we don’t have support for replicating data via APIs.** A workaround would be to have custom code to replicate the data from the API to a PostgreSQL instance, then sync that with PowerSync. We may add a way in the future to replicate the data directly from an API to the PowerSync Service, without a database in between.
   </Accordion>
 
-  <Accordion title="Are "live queries" supported?">
+  <Accordion title="Are live queries supported?">
     **Yes.** The PowerSync client SDKs support real-time streaming of changes, and can automatically rerun a query if the underlying data changed.It does not support incrementally updating the result set yet, but it should be fast if the query is indexed appropriately, and the result set is small enough.
   </Accordion>