* Update M2M FAQ
This is with regards to setting up the expectations like "We cannot commit on any deadlines" though we are sure of the approach after weighing the ramifications. Make it clear that M2M use case are diverse and its demand for new Util API.
* Update link to isMobileNumberPortableRegion
Link was pointing to line 3275, but that function is now on line 3524.
* Make isMobileNumberPortableRegion a permalink
* Update FAQ.md
* Add FAQ for number removals
Someone reported this recently and filing through Issue Tracker will anonymize the report.
* clarify example number usage
* Add FAQ about range overlaps
Specific examples about AR and MX provide since they are countries with varied lengths, formats and prefixes depending on context.
* Range overlaps updates
Integrated feedback from @lararennie
* FIXED_LINE_OR_MOBILE reference
* last cleanup
* Update M2M FAQ with more specific requests
Add more context how it's not just more metadata sources/countries we need, but also how to technically support M2M.
* Add example of M2M challenges
* Update FAQ.md
* remove mystery whitespace
from the start of a phone number.
Relevant for the many issues lately complaining about this behaviour for German numbers (country code 49) e.g. #1335 and #1067, etc