docs: improvements to the getting-started tutorial

This does two things:

1. Removes mentions of the communitytc instance. We don't want to direct
   new projects over to the community instance at this time.

2. Re-orders the steps. Previously the tutorial said to connect your
   repo to Taskcluster *and then* add tasks, but this is the wrong order
   because the repo needs to have a `tc.yml` file in order for
   fxci-config generation to succeed. So the order is now:

   a. Create tasks
   b. Request Scopes
   c. Connect to Github

Author: ahal

docs/tutorials/getting-started.rst

@@ -13,91 +13,85 @@ with your repo in as few steps as possible.
 
 There are three steps to getting running tasks:
 
-1. Install Taskcluster Github
+1. Define Tasks
 2. Request Permissions
-3. Define Tasks
+3. Install Taskcluster Github
 
 Let's dive into each!
 
-Install Taskcluster Github
---------------------------
+Create Tasks
+------------
 
-.. note::
+The first step is to define your tasks. You'll need:
 
-   If you are not using Github, skip to the next section.
+1. A :term:`Decision Task` defined in ``.taskcluster.yml``
+2. A Taskgraph setup in the ``taskcluster`` directory
+Luckily Taskgraph provides an ``init`` command that can generate both of these
+things automatically! Run:
 
-Each Taskcluster deployment has an associated Github app that needs to be added
-to your repo. Some apps for known Taskcluster deployments are as follows:
+.. code-block:: shell
 
-.. list-table:: Taskcluster Github Apps
-   :widths: 20 60
-   :header-rows: 1
+   $ pip install taskcluster-taskgraph
+   $ taskgraph init
 
-   * - Instance
-     - Github App
-   * - `Firefox-CI <https://firefox-ci-tc.services.mozilla.com>`_
-     - https://github.com/apps/firefoxci-taskcluster
-   * - `Community <https://community-tc.services.mozilla.com>`_
-     - https://github.com/apps/community-tc-integration
+This will automatically generate all the necessary files. Commit what was
+generated:
 
-Follow the link to the Github app for your deployment and click ``Configure``
-near the top right. Then select the repository you'd like to enable. If you are
-not an admin of the organization you are enabling the repo for, this will send
-a request to your Github administrators.
+.. code-block:: shell
 
-.. note::
+   $ git add .
+   $ git commit -m "Add Taskcluster files"
 
-   If you do not see a ``Configure`` button, contact your Github administrators
-   for assistance.
+Land your changes on the default branch (typically ``main``). Nothing will
+happen yet, but we need that ``.taskcluster.yml`` file to exist at the root of
+the repository for the next step.
 
 Request Permissions
 -------------------
 
-Your repository is now connected to Taskcluster, but it won't have permission
-to run anything. In the Taskcluster world, permissions are also known as
-:term:`scopes <Scope>`. So the next step is to contact your Taskcluster
-administrators and request scopes for your project so that it has access to the
-resources it needs to run tasks.
-
-Each Taskcluster instance can be managed differently, but here are the processes
-to request scopes for some known Taskcluster deployments:
+Your repository now has some tasks defined, but it won't have permission to run
+anything. In the Taskcluster world, permissions are also known as :term:`scopes
+<Scope>`. So the next step is to contact your Taskcluster administrators and
+request scopes for your project so that it has access to the resources it needs
+to run tasks.
 
-.. list-table:: Taskcluster Github Apps
-   :widths: 20 60
-   :header-rows: 1
+.. note::
 
-   * - Instance
-     - Process
-   * - `Firefox-CI <https://firefox-ci-tc.services.mozilla.com>`_
-     - `File a Bug <https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Firefox-CI%20Administration>`_
-   * - `Community <https://community-tc.services.mozilla.com>`_
-     - `File an Issue <https://github.com/taskcluster/community-tc-config/issues/new>`_
+   For Mozilla's `Firefox-CI <https://firefox-ci-tc.services.mozilla.com>`_ instance,
+   file a bug under `Release Engineering :: Firefox-CI Administration
+   <https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Firefox-CI%20Administration>`_
 
-Use a title such as: *Please setup `org/my-repo` with Taskcluster*.
+   Use a title such as: *Please setup `org/my-repo` with Taskcluster*.
 
-Create Tasks
-------------
+Install Taskcluster Github
+--------------------------
 
-The last step is to define your tasks. You'll need:
+.. note::
 
-1. A :term:`Decision Task` defined in ``.taskcluster.yml``
-2. A Taskgraph setup in the ``taskcluster`` directory
+   If you are not using Github, skip this section and reach out to your
+   Taskcluster administrators, there may be other steps to integrate your
+   repository.
 
-Luckily Taskgraph provides an ``init`` command that can generate both of these
-things automatically! Run:
+Each Taskcluster deployment has an associated Github app that needs to be added
+to your repo. If you are unsure which app your deployment uses, ask your
+Taskcluster administrators.
 
-.. code-block:: shell
+.. note::
 
-   $ pip install taskcluster-taskgraph
-   $ taskgraph init
+   The Github app for Mozilla's `Firefox-CI
+   <https://firefox-ci-tc.services.mozilla.com>`_ instance can be found here:
+   
+   https://github.com/apps/firefoxci-taskcluster
 
-This will automatically generate all the necessary files. Commit what was
-generated:
+Open the page of the Github app for your deployment and click ``Configure``
+near the top right. Then select the repository you'd like to enable. If you are
+not an admin of the organization you are enabling the repo for, this will send
+a request to your Github administrators.
 
-.. code-block:: shell
+.. note::
 
-   $ git add .
-   $ git commit -m "Add Taskcluster files"
+   If you do not see a ``Configure`` button, contact your Github administrators
+   for assistance.
 
 Now when you push, you should have a working Decision task that generates a
 ``hello-world`` task as well as a ``docker-image`` task that it depends on!