Docs update, fixup styling, mention free

Some minor updates following up on the last PR to docs.

docs/source/deploying.rst

@@ -151,7 +151,8 @@ See :doc:`deploying-cloud` for more details.
     Deploy Dask on YARN clusters, such as are found in traditional Hadoop installations.
 - `Dask Cloud Provider <https://cloudprovider.dask.org/en/latest/>`_
     Constructing and managing ephemeral Dask clusters on AWS, DigitalOcean, Google Cloud, Azure, and Hetzner
-- You can use `Coiled <https://coiled.io?utm_source=dask-docs&utm_medium=deploying>`_, a commercial Dask deployment option, to handle the creation and management of Dask clusters on cloud computing environments (AWS and GCP).
+- `Coiled <https://coiled.io?utm_source=dask-docs&utm_medium=deploying>`_
+    Commercial Dask deployment option, which handles the creation and management of Dask clusters on cloud computing environments (AWS and GCP).
 
 Ad-hoc deployments
 ~~~~~~~~~~~~~~~~~~

docs/source/faq.rst

@@ -426,59 +426,13 @@ Dask's custom APIs, notably :doc:`Delayed <delayed>` and :doc:`Futures
 
 See the section :doc:`gpu`.
 
-
-How do I cite Dask?
-~~~~~~~~~~~~~~~~~~~
-
-Dask is developed by many people from many institutions.  Some of these
-developers are academics who depend on academic citations to justify their
-efforts.  Unfortunately, no single citation can do all of these developers (and
-the developers to come) sufficient justice.  Instead, we choose to use a single
-blanket citation for all developers past and present.
-
-To cite Dask in publications, please use the following::
-
-   Dask Development Team (2016). Dask: Library for dynamic task scheduling
-   URL https://dask.org
-
-A BibTeX entry for LaTeX users follows::
-
-   @Manual{,
-     title = {Dask: Library for dynamic task scheduling},
-     author = {{Dask Development Team}},
-     year = {2016},
-     url = {https://dask.org},
-   }
-
-The full author list is available using ``git`` (e.g. ``git shortlog -ns``).
-
-
-Are there papers about Dask?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Rocklin, Matthew. "Dask: Parallel Computation with Blocked algorithms and Task
-Scheduling." (2015).
-`PDF <https://conference.scipy.org/proceedings/scipy2015/pdfs/matthew_rocklin.pdf>`_.
-
-::
-
-   @InProceedings{ matthew_rocklin-proc-scipy-2015,
-     author    = { Matthew Rocklin },
-     title     = { Dask: Parallel Computation with Blocked algorithms and Task Scheduling },
-     booktitle = { Proceedings of the 14th Python in Science Conference },
-     pages     = { 130 - 136 },
-     year      = { 2015 },
-     editor    = { Kathryn Huff and James Bergstra }
-   }
-
-
 For Marketing
 -------------
 
 There is a special subsite dedicated to addressing marketing concerns. You can
-find it at `marketing.dask.org <https://marketing.dask.org>`_.
+find it at `dask.org/brand-guide <https://dask.org/brand-guide>`_.
 
-Do you have any standardized logos?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Where can I find logos?
+~~~~~~~~~~~~~~~~~~~~~~~
 
 Yes! You can find them at :doc:`logos`.

docs/source/index.rst

@@ -302,8 +302,7 @@ Learn more at :bdg-link-primary:`Deploy Documentation <deploying.html>`
 
         Several companies offer commercial Dask products.  These are not open
         source, but tend to be easier, safer, cheaper, more fully featured,
-        etc..
-        Here is an incomplete list.
+        etc..  All options here include solid free offerings for individuals.
 
         .. _Coiled: https://coiled.io/?utm_source=dask-docs&utm_medium=homepage
         .. |coiled| replace:: **Coiled**
@@ -313,8 +312,9 @@ Learn more at :bdg-link-primary:`Deploy Documentation <deploying.html>`
         .. |nebari| replace:: **Nebari**
 
         -  |Coiled|_ provides a standalone Dask deployment product that works
-           in AWS and GCP.  Coiled notably employs most of the active Dask
-           maintainers today.
+           in AWS and GCP.
+
+           Coiled notably employs many of the active Dask maintainers today.
 
            Learn more at :bdg-link-primary:`Coiled <https://coiled.io>`