MX stopped supporting all additional dialing codes (01/02/044/045/1). Removed it from metadata as per b/295205666.

MX stopped supporting all additional dialing codes (01/02/044/045/1). Removed it from metadata as per b/295205666.

The issue links are dead since they point to the issues page for the GitHub page which is turned off.

The issue links are dead since they point to the issues page for the GitHub page which is turned off.

* Fixing anchors

Co-authored-by: penmetsaa <penmetsaa@google.com>

* Fixing anchors

Co-authored-by: penmetsaa <penmetsaa@google.com>

* Adding anchors for all FAQ entries (down to ###)

* Adding anchors for all FAQ entries (down to ###)

* M2M documentation update after NL M2M range support in mobile category

* Update FAQ.md

* M2M documentation update after NL M2M range support in mobile category

* Update FAQ.md

This is inspired from b/205606725 and older b/111967450 where MX stopped supporting all additional dialling codes.

This is inspired from b/205606725 and older b/111967450 where MX stopped supporting all additional dialling codes.

* Update FAQ about "why parsed national number is different in JS".

Inspired from https://issuetracker.google.com/issues/198423548

* Update FAQ.md

* Update FAQ about "why parsed national number is different in JS".

Inspired from https://issuetracker.google.com/issues/198423548

* Update FAQ.md

* 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 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.

Inspired from https://issuetracker.google.com/u/0/issues/129654594 where we mark a invalid number as valid but do not provide formatting.

Inspired from https://issuetracker.google.com/u/0/issues/129654594 where we mark a invalid number as valid but do not provide formatting.

* 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

* 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

Due to migration from Github issues to Issue Tracker.

Due to migration from Github issues to Issue Tracker.

* New formatting FAQ

To reformat or not to reformat?

* s/GitHub issue/issue

as per review suggestion

* New formatting FAQ

To reformat or not to reformat?

* s/GitHub issue/issue

as per review suggestion

Brought up in issue #1539

* 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

Linking to FAQ from the README, and updating broken links in the two files while here.

Adding FAQ about why we don't support countries like Bouvet Island, Yugoslavia, Antarctica etc. and what our rationale is for supporting a country.