Spruce up Readme

Also, added a Comment section

README.md

@@ -1,18 +1,21 @@
 # IPFS - FAQ
 
-This is the IPFS FAQ page. Please ask your question in an [Issue](https://github.com/ipfs/faq/issues). Make sure to search, as your question may already have been answered.
-
-Useful Links:
-### - [View Questions + Answers](https://github.com/ipfs/faq/issues)
-### - [Ask a new Question](https://github.com/ipfs/faq/issues/new) (please search first!)
+Please ask your question in an [Issue](https://github.com/ipfs/faq/issues). Make sure to search existing issues, as your question may already have been asked and answered.
 
+### [View Questions + Answers](https://github.com/ipfs/faq/issues)
+### [Ask a new Question](https://github.com/ipfs/faq/issues/new)
+_Please search first!_
 
 ## Notes:
 
-#### Rendering to a page
+#### Comment!
 
-All these questions and answers will be compiled into a webpage rendered at http://ipfs.io/docs/install (still TODO)
+There are a lot of questions, and it is difficult for the IPFS team to go through the backlog and refine answers for older questions. If you think a question hasn't been answered adequately, comment on it, and we'll look at it. Unlike on the rest of GitHub, using :thumb: or '+1' is actively encouraged as a way to show that a question should be brought back to our attention.
 
-#### use "WIP" in the question title to denote a "Work In Progress" answer.
+#### Use "WIP" in the question title to denote a "Work In Progress" answer.
 
 Let's mark any Q/As with `WIP` when the answer is long, complex, and likely to evolve over time. It is very important to signal when we think something is roughly "a final answer", versus "a place to jot down notes and point others for quick disambiguation". Many answers, like comparisons to other systems, will be WIPs for a while.
+
+#### Rendering to a page
+
+All these questions and answers will be compiled into a webpage rendered at http://ipfs.io/docs/install (still TODO)