Add WordPress trademark rules to naming guidance, issue : #152

[lai95]

What this changes

Adds a trademark note warning against using "WordPress" inside product names.

This expands the "Boring Descriptive Names" anti-pattern by showing that overly descriptive naming can introduce not only strategic weakness (lack of memorability) but also legal / trademark risk.

Also adds a short WordPress naming restrictions section in the availability guidance to reinforce correct usage patterns such as "[Product Name] for WordPress".

Which files

anti-patterns.md
availability.md

Checklist

• [ x] I've read CONTRIBUTING.md
• Cross-references to other files are updated (if applicable)
• New content uses real product names as examples (not hypothetical)
• Case studies include source links

Closes #152

[glacierphonk]

Thanks for the contribution @lai95 — content looks good and matches what #152 asked for. Two things to fix before this can merge:

1. Lint failure (MD007): The list items on anti-patterns.md lines 37-38 have 1-space indent — remove the leading space so they start at column 0. You can verify locally with markdownlint-cli2 '**/*.md'
2. Missing link: The "Check:" line in availability.md should be a hyperlink: [WordPress Trademark Policy](https://wordpressfoundation.org/trademark-policy/)

Minor note: check that the email in your git config (git config user.email) matches one of the emails listed at https://github.com/settings/emails — if it doesn't, update it before pushing the fixes so you get contributor credit after merge.

[lai95]

Greetings,

I fixed the spaces and added the hyperlink.

Also checked my emails, and they match!

[glacierphonk]

Thanks for the quick fix @lai95 — hyperlink and list formatting in availability.md look good now. Three small things left in anti-patterns.md before this can merge:

1. Leading space on line 36: The **WordPress Trademark:** line starts with a space ( **WordPress...), making it appear indented relative to its own bullet points below. Remove the leading space so it starts at column 0.

2. Missing em dash on line 36: "generic -it can" should be "generic — it can" (em dash —, not a hyphen). The rest of the document uses em dashes consistently.

3. Trailing double-spaces on lines 36–37: Two trailing spaces create hard line breaks in markdown. This file uses blank lines between paragraphs instead — remove the trailing spaces for consistency.

All minor — one more push and this is good to go.

[lai95]

Hey, couldnt see a visible difference by removing the double spaces.
Hope everything is alright now.

[glacierphonk]

.

Dismissed — posted in error.

[glacierphonk]

Looks good — thanks for sticking with the fixes across multiple rounds.