From 63714cb2b7b15dfa8e10bf017efda03b9b25558d Mon Sep 17 00:00:00 2001 From: Simon Willison Date: Wed, 10 Apr 2024 17:04:55 -0700 Subject: [PATCH] Fixed some typos spotted by Gemini Pro 1.5, closes #2318 --- docs/authentication.rst | 2 +- docs/internals.rst | 2 +- docs/plugin_hooks.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/authentication.rst b/docs/authentication.rst index a8dc5637..5452b9c3 100644 --- a/docs/authentication.rst +++ b/docs/authentication.rst @@ -312,7 +312,7 @@ If you want to provide access to any actor with a value for a specific key, use } .. [[[end]]] -You can specify that only unauthenticated actors (from anynomous HTTP requests) should be allowed access using the special ``"unauthenticated": true`` key in an allow block (`allow demo `__, `deny demo `__): +You can specify that only unauthenticated actors (from anonymous HTTP requests) should be allowed access using the special ``"unauthenticated": true`` key in an allow block (`allow demo `__, `deny demo `__): .. [[[cog from metadata_doc import config_example diff --git a/docs/internals.rst b/docs/internals.rst index 5cdf49b4..b57a289a 100644 --- a/docs/internals.rst +++ b/docs/internals.rst @@ -1234,7 +1234,7 @@ The datasette.utils module The ``datasette.utils`` module contains various utility functions used by Datasette. As a general rule you should consider anything in this module to be unstable - functions and classes here could change without warning or be removed entirely between Datasette releases, without being mentioned in the release notes. -The exception to this rule is anythang that is documented here. If you find a need for an undocumented utility function in your own work, consider `opening an issue `__ requesting that the function you are using be upgraded to documented and supported status. +The exception to this rule is anything that is documented here. If you find a need for an undocumented utility function in your own work, consider `opening an issue `__ requesting that the function you are using be upgraded to documented and supported status. .. _internals_utils_parse_metadata: diff --git a/docs/plugin_hooks.rst b/docs/plugin_hooks.rst index ada2fdbd..78489d1e 100644 --- a/docs/plugin_hooks.rst +++ b/docs/plugin_hooks.rst @@ -494,7 +494,7 @@ This will register ``render_demo`` to be called when paths with the extension `` ``render_demo`` is a Python function. It can be a regular function or an ``async def render_demo()`` awaitable function, depending on if it needs to make any asynchronous calls. -``can_render_demo`` is a Python function (or ``async def`` function) which accepts the same arguments as ``render_demo`` but just returns ``True`` or ``False``. It lets Datasette know if the current SQL query can be represented by the plugin - and hence influnce if a link to this output format is displayed in the user interface. If you omit the ``"can_render"`` key from the dictionary every query will be treated as being supported by the plugin. +``can_render_demo`` is a Python function (or ``async def`` function) which accepts the same arguments as ``render_demo`` but just returns ``True`` or ``False``. It lets Datasette know if the current SQL query can be represented by the plugin - and hence influence if a link to this output format is displayed in the user interface. If you omit the ``"can_render"`` key from the dictionary every query will be treated as being supported by the plugin. When a request is received, the ``"render"`` callback function is called with zero or more of the following arguments. Datasette will inspect your callback function and pass arguments that match its function signature.