Merge pull request #537 from permitio/update-logo

Update Logo and Branding

README.md

@@ -1,5 +1,5 @@
 <p  align="center">
- <img src="https://i.ibb.co/BGVBmMK/opal.png" height=170 alt="opal" border="0" />
+ <img src="https://github.com/permitio/opal/assets/4082578/4e21f85f-30ab-43e2-92de-b82f78888c71" height=170 alt="opal" border="0" />
 </p>
 <h1 align="center">
 ⚡OPAL⚡
@@ -100,19 +100,17 @@ curl -L https://raw.githubusercontent.com/permitio/opal/master/docker/docker-com
 
   - [How to configure OPAL (basic concepts)](https://docs.opal.ac/tutorials/configure_opal)
 
+  - [How to Use OPAL with Cedar in a Multi-Language Project](https://www.permit.io/blog/scaling-authorization-with-cedar-and-opal)
+
 - 🎨 &nbsp; [Key concepts and design](https://docs.opal.ac/overview/design)
 - 🏗️ &nbsp; [Architecture](https://docs.opal.ac/overview/architecture)
-
-      OPAL  uses a client-server stateless architecture. OPAL-Servers publish policy and data updates over a lightweight (websocket) PubSub Channel, which OPAL-clients subscribe to via topics. Upon updates each client fetches data directly (from source) to load it in to its managed OPA instance.
-
-  <br>
+<be>
+<br>
+OPAL  uses a client-server stateless architecture. OPAL-Servers publish policy and data updates over a lightweight (websocket) PubSub Channel, which OPAL-clients subscribe to via topics. Upon updates each client fetches data directly (from source) to load it in to its managed OPA instance.
   <br>
-
-<img src="https://i.ibb.co/CvmX8rR/simplified-diagram-highlight.png" alt="simplified" border="0">
-
+<img src="https://github.com/permitio/opal/assets/4082578/99d3dd95-a7ff-45c2-805e-3d533f8b1e8c" alt="simplified" border="0">
 <br>
-
-- 📖 &nbsp; For further reading check out our [Blog](https://bit.ly/opal_blog).
+📖 &nbsp; For further reading check out our [Blog](https://bit.ly/opal_blog).
 
 ## Community