Fix images on OpenSearch and Sentry (#187)

Author: danciaclara

images/open-search/opensearch-flow.webp

@@ -249,26 +249,7 @@ Instead, Plane batches updates through Redis. When a signal fires, the update go
 The batching pattern also provides resilience. If OpenSearch is temporarily unavailable, updates accumulate in Redis and process once connectivity returns. This requires Redis 6.2+ which supports the LPOP count operation needed for efficient batch retrieval.
 
 ### The complete flow
-```
-┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
-│   Plane Web     │────▶│   Plane API     │────▶│   OpenSearch    │
-│    (Search)     │     │   (Query)       │     │   (Indices)     │
-└─────────────────┘     └─────────────────┘     └─────────────────┘
-                               │
-                               │ Database signals
-                               ▼
-                        ┌─────────────────┐
-                        │   Redis Queue   │
-                        │   (Batching)    │
-                        └─────────────────┘
-                               │
-                               │ Celery task (every 5s)
-                               ▼
-                        ┌─────────────────┐
-                        │  Celery Worker  │────▶ Batch updates
-                        │  (Processing)   │
-                        └─────────────────┘
-```
+![OpenSeach flow](/images/open-search/opensearch-flow.webp)
 
 When you search, queries bypass this synchronization process entirely. The Plane API sends your search query directly to OpenSearch, which returns results almost instantly. Your database isn't involved in search queries at all — this is the key to search performance.
 

images/sentry/public-integration.webp

@@ -43,6 +43,8 @@ A custom integration (also called a public integration) connects your Sentry org
     Replace `[YOUR_DOMAIN]` with your actual Plane instance domain. For example, if your Plane instance is at `plane.company.com`, your Webhook URL would be `https://plane.company.com/silo/api/sentry/sentry-webhook/`
     </Note>
 
+    ![Public integration](/images/sentry/public-integration.webp)
+
 **Field explanations:**
 
 **Webhook URL**  
@@ -236,6 +238,8 @@ Configure these permissions to allow Sentry to interact with Plane appropriately
 | **Member** | Read | Access member details for assignee functionality |
 | **Alerts** | Read | Enable alert rule actions for automatic issue creation |
 
+![Sentry integration permissions](/images/sentry/sentry-permissions.webp)
+
 ### Enable webhooks
 
 Webhooks keep Plane and Sentry synchronized. When issues change in Sentry, Plane receives notifications and updates accordingly.
@@ -250,6 +254,8 @@ Enable the **issue** webhook with these events:
 | **archived** | Reflect archived status in Plane |
 | **unresolved** | Update Plane when resolved issues reopen |
 
+![Sentry webhook configuration](/images/sentry/sentry-webhook-config.webp)
+
 ### Save and retrieve credentials
 
 After saving your integration, Sentry generates OAuth credentials: