K8s network mapper tutorial new screenshots and text edit (#122)

docs/quick-tutorials/k8s-network-mapper.mdx

@@ -86,15 +86,15 @@ If you've attached Otterize OSS to Otterize Cloud, you can now also see the [acc
 
 ![Access graph](/img/quick-tutorials/network-mapper/otterize-tutorial-access-graph.png)
 
-Note, for example, that the `client` → `server` arrow has a yellow notification icon indicating a single notification. Clicking on it shows:
-
-<img src="/img/quick-tutorials/network-mapper/otterize-tutorial-access-graph-insights.png" alt="Access graph insights" width="600"/>
-
 The access graph reveals several types of information and insights, such as:
 1. Seeing the network map for different clusters, seeing the subset of the map for a given namespace, or even &mdash; according to how you've mapped namespaces to environments &mdash; seeing the subset of the map for a specific environment.
 2. Filtering the map to include recently-seen traffic, since some date in the past. That way you can eliminate calls that are no longer relevant, without having to reset the network mapper and start building a new map.
 3. If the intents operator is also connected, the access graph now reveals more specifics about access: understand which services are protected or would be protected, and which client calls are being blocked or would be blocked. We'll see more of that in the next couple of tutorials
 
+Note, for example, that the `client` &rightarrow; `server` arrow is yellow. Clicking on it shows:
+
+<img src="/img/quick-tutorials/network-mapper/otterize-tutorial-access-graph-edge-info-modal.png" alt="Client to server edge info" />
+
 ## What's next
 
 The network mapper is a great way to bootstrap IBAC. It generates client intents files that reflect