Add info for buffered flag; be consistent in examples

[Elchi3]

Description

This PR makes updates to the PerformanceResourceTiming and PerformanceServerTiming examples to explain why it is a good idea to use the buffered flag. It also makes the language consistent and avoids fragment sentences.

This is in response to feedback from previous PRs. Thank you, Joe and Will.

Motivation

openwebdocs/project#62

Additional details

The PerformanceServerTiming examples are interesting as they want multiple types and buffered. I wrapped the observe call in a forEach.

Related issues and pull requests

Previous PRs where this came up, e.g. #22683 (comment).

[github-actions]

Preview URLs (27 pages)

• /en-US/docs/Web/API/PerformanceResourceTiming/connectEnd
• /en-US/docs/Web/API/PerformanceResourceTiming/connectStart
• /en-US/docs/Web/API/PerformanceResourceTiming/decodedBodySize
• /en-US/docs/Web/API/PerformanceResourceTiming/domainLookupEnd
• /en-US/docs/Web/API/PerformanceResourceTiming/domainLookupStart
• /en-US/docs/Web/API/PerformanceResourceTiming/encodedBodySize
• /en-US/docs/Web/API/PerformanceResourceTiming/fetchStart
• /en-US/docs/Web/API/PerformanceResourceTiming/initiatorType
• /en-US/docs/Web/API/PerformanceResourceTiming/nextHopProtocol
• /en-US/docs/Web/API/PerformanceResourceTiming/redirectEnd
• /en-US/docs/Web/API/PerformanceResourceTiming/redirectStart
• /en-US/docs/Web/API/PerformanceResourceTiming/renderBlockingStatus
• /en-US/docs/Web/API/PerformanceResourceTiming/requestStart
• /en-US/docs/Web/API/PerformanceResourceTiming/responseEnd
• /en-US/docs/Web/API/PerformanceResourceTiming/responseStart
• /en-US/docs/Web/API/PerformanceResourceTiming/responseStatus
• /en-US/docs/Web/API/PerformanceResourceTiming/secureConnectionStart
• /en-US/docs/Web/API/PerformanceResourceTiming/serverTiming
• /en-US/docs/Web/API/PerformanceResourceTiming/toJSON
• /en-US/docs/Web/API/PerformanceResourceTiming/transferSize
• /en-US/docs/Web/API/PerformanceResourceTiming/workerStart
• /en-US/docs/Web/API/PerformanceResourceTiming
• /en-US/docs/Web/API/PerformanceServerTiming/description
• /en-US/docs/Web/API/PerformanceServerTiming/duration
• /en-US/docs/Web/API/PerformanceServerTiming/name
• /en-US/docs/Web/API/PerformanceServerTiming/toJSON
• /en-US/docs/Web/API/PerformanceServerTiming

Flaws (1)

Note! 26 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/API/PerformanceResourceTiming/responseStatus
Title: PerformanceResourceTiming.responseStatus
Flaw count: 1

• bad_bcd_queries:
  • No BCD data for query: api.PerformanceResourceTiming.responseStatus

(comment last updated: 2022-12-06 12:36:54)

[wbamberg]

👍 thank you Florian!