chore: use reserved values for phone numbers and domains where possible

[bsmth]

We should be using example domains instead of real URLs where possible.

[pepelsbey]

LGTM 👍

[estelle]

Using example.com, http://example.com/, @example.com for examples is generally a good idea, especially in the case of emails. That said, URLs that give contextual support (or provide entertainment without being promotional) shouldn’t be replaced.

Also, good catch on the phone number. TIL: "The North American Numbering Plan reserves 555-01 numbers for fictitious purposes. "

[bsmth]

Using example.com, http://example.com/, @example.com for examples is generally a good idea, especially in the case of emails. That said, URLs that give contextual support (or provide entertainment without being promotional) shouldn’t be replaced.

Yeah I think this makes sense, I've reverted most of the wiki links, but I agree, with emails and telephone numbers, we should use reserved values.

I presume it's also important what the example is doing (fetch or others that are actually making requests should only use example.com, I guess.)

[bsmth]

I'm going ahead to merge this one after incorporating the feedback! TY 👍🏻

[Jxck]

Using example.com, http://example.com/, @example.com for examples is generally a good idea, especially in the case of emails. That said, URLs that give contextual support (or provide entertainment without being promotional) shouldn’t be replaced.

If real traffic happens from document, testing, demo etc will suffer domain owners. This is especially true for sites like MDN, which are used by many users.
Example domains are standardized for this purpose in RFC6761.
MDN should respect it.

When you require some context, *.example can be used like wiki.example, movie.example etc.
I'll re-revert some changes above in separate PR.
If you require more discussion, https://github.com/orgs/mdn/discussions/450 is the best place.