finbox-in · ChiragRayani · May 21, 2025 · May 21, 2025 · May 21, 2025
diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
@@ -8,7 +8,7 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@v2
 

diff --git a/docs/.vuepress/public/Device_connect_architecture.jpg b/docs/.vuepress/public/Device_connect_architecture.jpg
diff --git a/docs/.vuepress/public/Permissions_screen.jpg b/docs/.vuepress/public/Permissions_screen.jpg
diff --git a/docs/.vuepress/public/device_connect_android_integration.jpg b/docs/.vuepress/public/device_connect_android_integration.jpg
diff --git a/docs/.vuepress/public/device_connect_android_integration.svg b/docs/.vuepress/public/device_connect_android_integration.svg
diff --git a/docs/.vuepress/public/device_connect_architecture.svg b/docs/.vuepress/public/device_connect_architecture.svg
diff --git a/docs/.vuepress/public/device_connect_back_end_integration.jpg b/docs/.vuepress/public/device_connect_back_end_integration.jpg
diff --git a/docs/.vuepress/public/device_connect_back_end_integration.svg b/docs/.vuepress/public/device_connect_back_end_integration.svg
diff --git a/docs/.vuepress/public/device_connect_frontend_server_integrations.svg b/docs/.vuepress/public/device_connect_frontend_server_integrations.svg
diff --git a/docs/.vuepress/public/device_connect_integration.svg b/docs/.vuepress/public/device_connect_integration.svg
diff --git a/docs/.vuepress/public/device_connect_permissions_screen.svg b/docs/.vuepress/public/device_connect_permissions_screen.svg
diff --git a/docs/.vuepress/public/permission_screen.png b/docs/.vuepress/public/permission_screen.png
diff --git a/docs/.vuepress/public/rest_api_workflow.png b/docs/.vuepress/public/rest_api_workflow.png
diff --git a/docs/device-connect/architecture.md b/docs/device-connect/architecture.md
@@ -8,7 +8,7 @@
 * **Real-Time Insights**: Leverage FinBox’s advanced feature engine to access actionable scores and predictions.
 * **Privacy-First Design**: Built to comply with stringent privacy standards, ensuring no Personally Identifiable Information (PII) is stored or shared.
 
-<img src="/Device_connect_architecture.jpg" alt="DeviceConnect Architecture" style="width:100%;height:100%" />
+<img src="/device_connect_architecture.svg" alt="DeviceConnect Architecture" style="width:100%;height:100%" />
 
 **How DeviceConnect Works** :
 

diff --git a/docs/device-connect/frontend-integration.md b/docs/device-connect/frontend-integration.md
@@ -4,7 +4,7 @@ DeviceConnect empowers businesses with real-time, anonymized data intelligence t
 
 The frontend integration process consists of three key steps.
 
-<img src="/device_connect_android_integration.jpg" alt="Device Connect Android Integration Workflow" style="width:80%;height:80%" />
+<img src="/device_connect_android_integration.svg" alt="Device Connect Android Integration Workflow" style="width:80%;height:80%" />
 
 ### Step 1: Requesting Runtime Permissions
 

diff --git a/docs/device-connect/insights-integration-flow.md b/docs/device-connect/insights-integration-flow.md
@@ -8,7 +8,7 @@ The **Insights API** allows clients to:
 
 An overview of the API calling is shown below
 
-<img src="/device_connect_back_end_integration.jpg" alt="Device Connect Backed Integration Workflow" />
+<img src="/device_connect_back_end_integration.svg" alt="Device Connect Backed Integration Workflow" />
 
 ### **Integration Workflow**
 

diff --git a/docs/device-connect/integration-flow.md b/docs/device-connect/integration-flow.md
@@ -16,7 +16,6 @@ DeviceConnect SDK Integration Summary:
 * Assign a unique, custom-generated user hash — no PII should be used or stored
 * Start periodic syncing to ensure data is sent to FinBox servers
 
-
 **3. Intelligent Data Synchronization**:
 
 * Once periodic syncing is enabled, anonymized device data is automatically sent to FinBox every 8 hours

diff --git a/docs/device-connect/permissions.md b/docs/device-connect/permissions.md
@@ -11,7 +11,7 @@ Additionally, include a link to the Privacy Policy at the bottom of the screen f
 
 Here’s an example structure for a Consent Screen
 
-<img src="/Permissions_screen.jpg" alt="Permission Screen" style="width:500;height:600" />
+<img src="/device_connect_permissions_screen.svg" alt="Permission Screen" style="width:500;height:600" />
 
 ### Runtime Permissions Added by the SDK
 Below are the list of Runtime permissions the sdk automatically adds to the application Manifest, if Manifest Merger is enabled:
-Original file line number
+Diff line change
@@ Expand Up / @@ -8,7 +8,7 @@ on: @@
     jobs:
       deploy:
-        runs-on: ubuntu-20.04
+        runs-on: ubuntu-22.04
         steps:
           - uses: actions/checkout@v2
@@ Expand Down @@