Remove BitBucket references from Firefox documentation

src/products/firefox_desktop/adding_nightly.md

@@ -17,11 +17,9 @@ Click the *Create Buglinks* button, and a set of links will appear at the bottom
 
 Always double check the content of the bugs for errors or outdated content. If the information is obsolete, you can update the templates in this [Wiki page](https://wiki.mozilla.org/L10n:Bugogram) (it will require a new deployment of Elmo to production to update the code generating the links).
 
-## Land initial content in l10n repository
+## Verify content in l10n repository
 
-With cross-channel, all builds of Firefox are generated using strings from the l10n-central repository. If a project started localizing using a BitBucket repository, it’s **fundamental** to populate l10n-central with that content when requesting the official repository creation on `https://hg.mozilla.org/l10n-central/LOCALE_CODE`.
-
-After the first content lands in l10n-central, it’s a good idea to perform some basic checks before enabling the build:
+Before enabling the build, it’s a good idea to perform some basic checks:
 * Check `toolkit/global/intl.properties` ([en-US version](https://hg.mozilla.org/mozilla-central/file/default/toolkit/locales/en-US/chrome/global/intl.properties)) for evident mistakes.
 * Check if there’s a `region.properties` file in `browser/chrome/browser-region/region.properties`, if needed replace it with the [stock version](../searchplugins/files/desktop_region.properties).
 

src/products/firefox_desktop/adding_pontoon.md

@@ -1,8 +1,7 @@
 # Adding a new locale to Pontoon
 
-Before addind a new locale to Pontoon, the `hg` repository needs to be already set up. For brand new locales:
-
-* Create a new public Mercurial repository in the [mozilla-l10n](https://bitbucket.org/mozilla-l10n/) organization on BitBucket.
-* Push at least one change to the repository, otherwise Pontoon will not pick it up during sync. The safest change it to initialize the `toolkit/chrome/global/intl.properties` file with the correct values ([example](https://bitbucket.org/mozilla-l10n/ppl/commits/b3fd0faf59b0b45b2cf30c01d85157beee2a0bd0 )).
+* If the locale is not [available](https://pontoon.mozilla.org/teams/) in Pontoon yet, [consult this document](../../tools/pontoon/adding_new_locale.md) for instructions on how to add it.
+* File a bug to create a new Mercurial repository in [l10n-central](https://hg.mozilla.org/l10n-central/). Several bug templates, including one to request a new repository, are available in [this page](https://l10n.mozilla.org/bugs/new-locale). For more information about these templates, [refer to this document](adding_nightly.md).
+* Push at least one change to the repository, otherwise Pontoon will not pick it up during sync. The safest change is to initialize the `toolkit/chrome/global/intl.properties` file with the correct values ([example](https://hg.mozilla.org/l10n-central/ppl/rev/b3fd0faf59b0b45b2cf30c01d85157beee2a0bd0)).
 
 Once the repository is available and contains at least one commit, the locale can be added to the Firefox project in Pontoon.

src/tools/pontoon/adding_new_locale.md

@@ -6,7 +6,7 @@ Access Django’s admin interface at `https://pontoon.mozilla.org/a/` (note that
 
 Before moving forward:
 * If the locale is going to work on mozilla.org, files need to be set up in [tools](../webdashboards/) and GitHub before enabling the project in Pontoon.
-* If the locale is going to work on Firefox, and an [official Mercurial repository](https://hg.mozilla.org/l10n-central/) is not available, a repository needs to be created in the [mozilla-l10n organization on BitBucket](https://bitbucket.org/mozilla-l10n/). Currently :pike, :mathjazz and :flod have permissions to create such repository.
+* If the locale is going to work on Firefox, it requires an [official Mercurial repository](https://hg.mozilla.org/l10n-central/).
 
 ## Add the new locale