The first question you linked has been closed as NARQ because it was too broad: It asks for the actual system requirements without even saying which modules the site is using. If with actual it means typically, answering would require to know which modules are typically installed; in this case, the question would be not constructive.
Generally, for questions that can be answered looking at the documentation, I would consider if:
- The documentation comes from a source you can trust
- The documentation is accessible from everybody, and it is the first thing you would expect the OP to check
- The documentation doesn't require any interpretation from the OP
- The answer doesn't need to do any other consideration, and it reports what the documentation says
For example, if the question is asking how to get absolute URLs from url() that would be a possible candidate for being closed at too localized, as few users would get any benefit from a question for which the answer would be repeating what the documentation says. Vice versa, a question where the OP shows s/he has read the documentation about
url() (but s/he still not able to understand why the code is not working) would not be a candidate for being closed as too localized, if not in the case the code is not working because a typo.
If there isn't any reason to close a question, down-voting is what you can do, as the tooltip says "This question does not show any research effort; it is unclear or not useful." I understand "not useful" as meaning "not useful to other users," not "not useful to me"; differently, a user who is a Drupal expert would down-vote every question because s/he doesn't find them useful.
I would not down-vote a question, if not in the case the question doesn't show any effort, which could also mean the OP doesn't show what s/he searched, what s/he tried, and the OP didn't put any effort for looking for a solution.