remove browser_first_contentful_paint

Author: mdcruz

src/data/markdown/translated-guides/en/03 Using k6 browser/03 Metrics.md

@@ -47,7 +47,7 @@ Existing browser measures such as the `Load` and `DOMContentLoaded` time do not
 
 <Blockquote mod="note" title="">
 
-  As of k6 version 0.44.0, k6 now natively supports [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals). In future releases, to align with recommended practices, we will remove the following browser metrics to focus on the web vital metrics. Please refer to [#831](https://github.com/grafana/xk6-browser/issues/831) for more information.
+  As of [k6 version 0.44.0](https://github.com/grafana/k6/releases/tag/v0.44.0), k6 now natively supports [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals). In future releases, to align with recommended practices, we will remove the following browser metrics to focus on the web vital metrics. Please refer to [#831](https://github.com/grafana/xk6-browser/issues/831) for more information.
 
 </Blockquote>
 
@@ -57,7 +57,6 @@ Apart from the usual HTTP specific metrics that k6 already tracks, the browser m
 |--------------------------------|--------------------------------------------------------------------------------------------------------------|
 | browser_dom_content_loaded     | Emitted when the page is loaded but scripts have just started to be executed.                                |
 | browser_first_paint            | Emitted when the browser renders the first pixel on the page.                                                |
-| browser_first_contentful_paint | Emitted when the browser renders the first DOM element on the page, whether that's a text, image or header.  |
 | browser_loaded                 | Emitted when the page is fully loaded.                                                                       |
 
 ## Understanding the browser metrics output