I don't think it's right to down vote questions just because they contain a certain word or phrase. I also don't think that questions should be edited to remove a certain word or phrase just because some people don't like it.
A down vote on a question means "this question does not show any research effort; it is unclear or not useful". If you feel that the question does not show research effort, it is unclear, or it is not useful outside of the specific case of the asker, then you should down vote it. If the question is extremely unclear, there's also a close reason for that purpose that you should also use.
I do agree that many people who are looking for "best practices" or specific "design patterns" for their situation don't understand the core nature of these things. Best practices are simply things that work for most (or even many) people most (or much) of the time, but that doesn't mean they work for everyone all of the time. Design patterns aren't things to be forced or used, it's a library of common types of problems and solutions that have often worked for solving them that have been seen multiple times to the point where they have been named and analyzed for easier communication.
When you come across a question asking for a "best practice" or a "design pattern", there are a few things to do.
If the question is answerable, answer it. If they have described the problem and situation in enough detail that you can present them with a good option and back that option up with facts, references, and/or experiences along with appropriate citations as necessary, provide that answer.
If the question is not answerable, leave a comment explaining why. I would link to appropriate, related questions here, on other SE sites, or articles on Wikipedia that give background and ask specific questions that I feel would need to be answered to move the question into an answerable state. If it's generally unanswerable, also feel free to cast a close vote - it's better to close quickly before it gets answers, edit the question to move it to a generally answerable state, and then reopen it so the answers are of a higher quality.
Here are some resources to link to, for various questions:
There may be plenty more good questions and articles out there, but these should be good for the types of question you bring up.
I was just brushing up on CMMI and I came across a footnote:
You usually hear about "best practices", right? Rich has spent several years attempting to change that terminology. In his experience, there is no such thing as a "best practice" -- only practices that have shown to be useful within a specific context. That same practice could be useless or even deterimental in another context...In any event, the term "best practice" is misleading. We prefer to use "successful" (or "unsuccessful") to describe practices that provide useful knowledge. Unsuccessful processes and practices are as critical to understand as successful processes and practices.
In this quote, Rich is referring to Dr. Richard Turner.
I agree with this quote - we should be encouraging people to not consider "best practices". Instead, we should encourage people to provide well-bounded contexts and describe the intended results, while sharing both successful and unsuccessful things that we have done and the contexts in which we have done them.
Changing people's words seems to be largely unnecessary since we should understand what the intention is - we should only directly change words if the original wording is not understandable or correct.