Minor edits to the "Third-party cookies" section

[DanKaplanSES]

• I think there was some issues with pluralization of the word "Cookie" at the end of this section, so I attempted to reword it.
• I ended up changing more than I originally intended
• I did not intend to change any of the original meaning. If I did, that was a mistake on my part.

[github-actions]

Preview URLs

• /en-US/docs/Web/HTTP/Guides/CORS

Flaws (1)

URL: /en-US/docs/Web/HTTP/Guides/CORS
Title: Cross-Origin Resource Sharing (CORS)
Flaw count: 1

• unknown:
  • No generic content config found

[hamishwillee]

I prefer your version, but it does kind of change the "flow". How about this (for the whole section)

Suggested change

	Third-party cookie policies (e.g., the [SameSite](/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#samesitesamesite-value) attribute) may suppress certain cookies from being sent to the server. The enforced cookie policy may therefore nullify the capability described in this chapter, effectively preventing you from making credentialed requests whatsoever.
	Cookies set in CORS requests and responses are subject to normal third-party cookie policies.
	Third-party cookie policies may prevent third party cookies being sent in requests, effectively stopping a site from making credentialed requests even if permitted by the third party server (using `Access-Control-Allow-Credentials`).
	The default policy differs between browsers, but may be set using the [SameSite](/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#samesitesamesite-value) attribute.
	Even if credentialed requests are allowed, a browser may be configured to reject all third-party cookies in responses.