Fix internal links

Author: pwseg

src/connections/destinations/catalog/actions-google-analytics-4-web/index.md

@@ -94,7 +94,7 @@ UTM Parameters are automatically tracked and sent to Google when they are presen
 
 Without any further configuration, traffic-source data for `campaign`, `campaign_id`, `content`, `medium`, and `source` will populate in GA4. This can be observed on Google's side by triggering a `Page` call with UTM parameters present in the URL and navigating to the **Realtime overview** report in GA4 to see the resulting `page_view` event under the _Event count by Event name_ card. 
 
-### Difference between Google Analytics 4 Cloud and Google Analytics 4 Web destinations 
+### Differences between Google Analytics 4 Cloud and Google Analytics 4 Web destinations 
 
-Segment's  [Google Analytics 4 Cloud](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, while Segment's [Google Analytics 4 Web](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4-web/) device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. There are advantages and disadvantages to each destination and your choice between the two will depend on your specific use case, technical expertise, and the platforms from which you want to track data.
+Segment's [Google Analytics 4 Cloud](/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, whereas Segment's [Google Analytics 4 Web](/docs/connections/destinations/catalog/actions-google-analytics-4-web/) device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. Each destination has its own advantages and disadvantages. Your choice between the two will depend on your specific use case, technical expertise, and the platforms from which you want to track data.