Update traffic events doc images

Author: braginini

public/docs-static/img/how-to-guides/traffic-events/network-resource-succesful-connection.png

@@ -76,7 +76,7 @@ the internal network resource.
 
 A slightly modified example of the CRM server connection scenario would be if instead of running the NetBird client on the CRM server,
 you used the [NetBird Networks feature](/how-to/networks) and created a network resource for the CRM server. In this case, if a user accessed an internal CRM from their laptop via a browser
-and port `5432`, NetBird would log the traffic events for that connection on the user's machine and the routing peer that
+and port 443, NetBird would log the traffic events for that connection on the user's machine and the routing peer that
 routed the connection to the CRM server. If the connection was blocked, NetBird would log the blocked event on the routing peer.
 
 <p>
@@ -87,11 +87,11 @@ routed the connection to the CRM server. If the connection was blocked, NetBird
 
 The screenshot below illustrates a successful connection from `Alice` to the network resource `CRM` running in the AWS VPC.
 The traffic is routed through a routing peer, which logs the connection event and reports it to the NetBird servers.
-The access is permitted by the policy `IT Admins to AWS Servers`, which allows connections over the `TCP` protocol on port `5432`.
+The access is permitted by the policy `IT Admins to AWS Servers`, which allows connections over the `TCP` protocol on port `443`.
 Note the `ROUTER` column in the table, which identifies the routing peer responsible for routing to the internal network resource.
 
 <p>
-    <img src="/docs-static/img/how-to-guides/traffic-events/network-resource-succesful-connection.png" alt="network-resource-succesful-connection" className="imagewrapper-big"/>
+    <img src="/docs-static/img/how-to-guides/traffic-events/network-resource-successful-connection.png" alt="network-resource-succesful-connection" className="imagewrapper-big"/>
 </p>
 
 <Note>
@@ -112,7 +112,7 @@ in one TCP session, but the routing peer blocked all attempts.
 
 <Note>
     For all the examples above, we used the `nc` command to initiate the connection to the CRM server from the peer `Alice`.
-    E.g., `nc -v crm.netbird.cloud 5432`.
+    E.g., `nc -v crm.netbird.cloud 443`.
 </Note>
 
 ## Enabling Traffic Events Logging