Fixed master -> main in a bunch of places, mainly docs

docs/contributing.rst

@@ -10,7 +10,7 @@ This document describes how to contribute to Datasette core. You can also contri
 General guidelines
 ------------------
 
-* **master should always be releasable**. Incomplete features should live in branches. This ensures that any small bug fixes can be quickly released.
+* **main should always be releasable**. Incomplete features should live in branches. This ensures that any small bug fixes can be quickly released.
 * **The ideal commit** should bundle together the implementation, unit tests and associated documentation updates. The commit message should link to an associated issue.
 * **New plugin hooks** should only be shipped if accompanied by a separate release of a non-demo plugin that uses them.
 

docs/custom_templates.rst

@@ -303,7 +303,7 @@ from the default template.
 
 The ``_table.html`` template is included by both the row and the table pages,
 and a list of rows. The default ``_table.html`` template renders them as an
-HTML template and `can be seen here <https://github.com/simonw/datasette/blob/master/datasette/templates/_table.html>`_.
+HTML template and `can be seen here <https://github.com/simonw/datasette/blob/main/datasette/templates/_table.html>`_.
 
 You can provide a custom template that applies to all of your databases and
 tables, or you can provide custom templates for specific tables using the

docs/datasette-package-help.txt

@@ -10,7 +10,7 @@ Options:
 
   -m, --metadata FILENAME   Path to JSON/YAML file containing metadata to publish
   --extra-options TEXT      Extra options to pass to datasette serve
-  --branch TEXT             Install datasette from a GitHub branch e.g. master
+  --branch TEXT             Install datasette from a GitHub branch e.g. main
   --template-dir DIRECTORY  Path to directory containing custom templates
   --plugins-dir DIRECTORY   Path to directory containing custom plugins
   --static MOUNT:DIRECTORY  Serve static files from this directory at /MOUNT/...

docs/datasette-publish-cloudrun-help.txt

@@ -5,7 +5,7 @@ Usage: datasette publish cloudrun [OPTIONS] [FILES]...
 Options:
   -m, --metadata FILENAME         Path to JSON/YAML file containing metadata to publish
   --extra-options TEXT            Extra options to pass to datasette serve
-  --branch TEXT                   Install datasette from a GitHub branch e.g. master
+  --branch TEXT                   Install datasette from a GitHub branch e.g. main
   --template-dir DIRECTORY        Path to directory containing custom templates
   --plugins-dir DIRECTORY         Path to directory containing custom plugins
   --static MOUNT:DIRECTORY        Serve static files from this directory at /MOUNT/...

docs/datasette-publish-heroku-help.txt

@@ -5,7 +5,7 @@ Usage: datasette publish heroku [OPTIONS] [FILES]...
 Options:
   -m, --metadata FILENAME         Path to JSON/YAML file containing metadata to publish
   --extra-options TEXT            Extra options to pass to datasette serve
-  --branch TEXT                   Install datasette from a GitHub branch e.g. master
+  --branch TEXT                   Install datasette from a GitHub branch e.g. main
   --template-dir DIRECTORY        Path to directory containing custom templates
   --plugins-dir DIRECTORY         Path to directory containing custom plugins
   --static MOUNT:DIRECTORY        Serve static files from this directory at /MOUNT/...

docs/plugin_hooks.rst

@@ -304,7 +304,7 @@ publish_subcommand(publish)
 This hook allows you to create new providers for the ``datasette publish``
 command. Datasette uses this hook internally to implement the default ``now``
 and ``heroku`` subcommands, so you can read
-`their source <https://github.com/simonw/datasette/tree/master/datasette/publish>`_
+`their source <https://github.com/simonw/datasette/tree/main/datasette/publish>`_
 to see examples of this hook in action.
 
 Let's say you want to build a plugin that adds a ``datasette publish my_hosting_provider --api_key=xxx mydatabase.db`` publish command. Your implementation would start like this:
@@ -641,7 +641,7 @@ Each Facet subclass implements a new type of facet operation. The class should l
 
             return facet_results, facets_timed_out
 
-See `datasette/facets.py <https://github.com/simonw/datasette/blob/master/datasette/facets.py>`__ for examples of how these classes can work.
+See `datasette/facets.py <https://github.com/simonw/datasette/blob/main/datasette/facets.py>`__ for examples of how these classes can work.
 
 The plugin hook can then be used to register the new facet class like this:
 

docs/publish.rst

@@ -78,7 +78,7 @@ Publishing to Vercel
     pip install datasette-publish-vercel
     datasette publish vercel mydatabase.db --project my-database-project
 
-Not every feature is supported: consult the `datasette-publish-vercel README <https://github.com/simonw/datasette-publish-vercel/blob/master/README.md>`__ for more details.
+Not every feature is supported: consult the `datasette-publish-vercel README <https://github.com/simonw/datasette-publish-vercel/blob/main/README.md>`__ for more details.
 
 .. _publish_fly:
 
@@ -92,7 +92,7 @@ Publishing to Fly
     pip install datasette-publish-fly
     datasette publish fly mydatabase.db
 
-Consult the `datasette-publish-fly README <https://github.com/simonw/datasette-publish-fly/blob/master/README.md>`__ for more details.
+Consult the `datasette-publish-fly README <https://github.com/simonw/datasette-publish-fly/blob/main/README.md>`__ for more details.
 
 .. _publish_custom_metadata_and_plugins:
 

docs/spatialite.rst

@@ -53,7 +53,7 @@ If you are unsure of the location of the module, try running ``locate mod_spatia
 Building SpatiaLite from source
 -------------------------------
 
-The packaged versions of SpatiaLite usually provide SpatiaLite 4.3.0a. For an example of how to build the most recent unstable version, 4.4.0-RC0 (which includes the powerful `VirtualKNN module <https://www.gaia-gis.it/fossil/libspatialite/wiki?name=KNN>`_), take a look at the `Datasette Dockerfile <https://github.com/simonw/datasette/blob/master/Dockerfile>`_.
+The packaged versions of SpatiaLite usually provide SpatiaLite 4.3.0a. For an example of how to build the most recent unstable version, 4.4.0-RC0 (which includes the powerful `VirtualKNN module <https://www.gaia-gis.it/fossil/libspatialite/wiki?name=KNN>`_), take a look at the `Datasette Dockerfile <https://github.com/simonw/datasette/blob/main/Dockerfile>`_.
 
 Spatial indexing latitude/longitude columns
 ===========================================