Review FAQ effectiveness

[iandunn]

In #119 we discussed some potential solutions to solving the confusion that is leading to inaccurate data, and decided to move forward with the FAQ, and see how effective it is. If it doesn't turn out to be, then we can circle back and consider some other solutions.

Once that issue is closed and there's been enough time to see if it's working or not, we can review the data and either consider it done, or iterate on the solutions.

[iandunn]

Ideas mentioned in #119 as potential future actions, if the ones there don't prove to be effective.

• Email people and ask them to update their data. Done manually in Prevent and remove spam/dormant pledges #169, will be done automatically in Regularly email contributors to prompt for updates #27
• Maybe automatically hide anyone who doesn't have a Slack account connected to their profile, since there's no way that a team rep could contact them to get them involved in a project. Or we could prevent people from confirming a pledge until they have a Slack account, and retroactively un-confirm people who don't have one. Before doing this, verify the assumption that there aren't active 5ftf contributors who don't use slack