Clean up TODOs in docs site (#48)

Author: EzraBrooks

source/Getting-Started.rst

@@ -1,15 +1,8 @@
 Getting Started
 ===============
 
-To get started with Space ROS development, you can either download a pre-built Docker image from Docker Hub, or build the Docker image yourself.
-The following pages describe each of these scenarios.
+To get started with Space ROS development, you can either download a pre-built Docker image from Docker Hub, or build the Docker image yourself using the instructions in the :doc:`First Time Building tutorial <Tutorials/First-Time-Building>`.
 
-.. toctree::
-   :titlesonly:
-   :maxdepth: 2
-
-   Getting-Started/Docker-Images
-   Getting-Started/Building-From-Source
+Pre-built Docker images are available from the `OSRF Space ROS page <https://hub.docker.com/r/osrf/space-ros>`_ on Docker Hub.
 
 Once you have a Docker image, you may want to review the :doc:`Demos <Demos>`, :doc:`Tutorials <Tutorials>`, and :doc:`How-To Guides <How-To-Guides>` to learn more about various Space ROS topics.
-

source/Getting-Started/Building-From-Source.rst

@@ -9,11 +9,9 @@ They contain succinct steps to help you accomplish important tasks quickly.
 .. toctree::
    :maxdepth: 1
 
-   How-To-Guides/Use-Custom-Allocator
    How-To-Guides/Reproducing-CI-Results
    How-To-Guides/Use-Cobra
    How-To-Guides/MC-DC-Testing-Tool
    How-To-Guides/Use-VSCode-With-Docker
    How-To-Guides/Use-The-Dashboard
-   How-To-Guides/Use-Simulation-Assets
    How-To-Guides/Releasing-Space-ROS

source/Getting-Started/Docker-Images.rst

@@ -17,8 +17,6 @@ The following sections describe the motivation for Space ROS, how Space ROS is d
 
    Introduction/About-Space-ROS
    Introduction/How-Space-ROS-Differs
-   Introduction/Dev-And-Release-Model
 
 .. image:: /images/viper-lights.png
    :alt: Artist's rendition of the VIPER rover on the surface of the moon
-

source/How-To-Guides.rst

@@ -4,7 +4,7 @@ Related Projects
 Space ROS makes use of several external projects that aren't part of standard ROS 2 distributions.
 The first pair of tools, IKOS and Cobra, are static analysis tools that have been integrated into Space ROS using the same Python wrapper method used for other code analysis tools integrated into standard ROS 2 distributions, such as clang-tidy and cpplint.
 The full set of code analysis tools are run automatically when building and running package tests ('colcon test').
-The next set of tools, Doorstop and FRET, are requirements tools that are part of an :doc:`overall requirements methodology <Tutorials/Requirements-Tools-And-Processes>` used for Space ROS.
+The next set of tools, Doorstop and FRET, are requirements tools used for Space ROS.
 The last tool, Ogma, is a runtime verification tool that produces monitoring applications for Space ROS.
 
 .. toctree::

source/How-To-Guides/Use-Custom-Allocator.rst

@@ -15,8 +15,6 @@ Why use Doorstop?
 Contributors to an open source project like Space ROS are unlikely to purchase expensive requirements management tools or use heavyweight requirements processes.
 Using the open source Doorstop tool to manage requirements helps to strike a balance between the need for strong processes to support certification, such as requirements traceability, and ease-of-contributing for the open source community.
 
-To learn more about how Doorstop is used in Space ROS, please refer to this tutorial on the `Requirements Tools and Processes <../Tutorials/Requirements-Tools-And-Processes>`_ used in Space ROS.
-
 Additional References
 ---------------------
 
@@ -25,4 +23,3 @@ Please refer to the following resources to learn more about Doorstop:
 * `Doorstop documentation <https://doorstop.readthedocs.io/en/latest/>`_
 * `The Doorstop github repository <https://github.com/doorstop-dev/doorstop>`_
 * `Doorstop: Text-Based Requirements Management Using Version Control <https://www.researchgate.net/publication/276044183_Doorstop_Text-Based_Requirements_Management_Using_Version_Control>`_
-