docs: fix more typos

2026-09-01 15:37:32 +08:00 · 2026-06-14 13:12:07 +00:00
parent 01afe742e3
commit a9861d7ddc
6 changed files with 9 additions and 9 deletions
@@ -26,7 +26,7 @@ If Galaxy complains about the version of Python you are using:
     ```sh
     % rm -rf /path/to/galaxy/database/compiled_templates/
     ```
-   These templated will be regenerated automatically when starting Galaxy.
+   These templates will be regenerated automatically when starting Galaxy.

 5. Start Galaxy again.

@@ -16,7 +16,7 @@
 :Description:
    Database connection. Galaxy Reports are intended for production
    Galaxy instances, so sqlite (and the default value below) is not
-    supported. An SQLAlchemy connection string should be used specify
+    supported. An SQLAlchemy connection string should be used to specify
    an external database.
 :Default: ``sqlite:///./database/universe.sqlite?isolation_level=IMMEDIATE``
 :Type: str
@@ -326,7 +326,7 @@ server within an InteractiveTool container now must serve the contents under a p
        When ``requires_path_in_url="True"`` in the ``entry_point`` tag, the InteractiveTool proxy service forwards the HTTP requests
        with the full path intact.

-    Both values of ``requires_path_in_url`` can be combined with both injection mechanisms, leading two four configuration variants
+    Both values of ``requires_path_in_url`` can be combined with both injection mechanisms, leading to four configuration variants
    for path-based InteractiveTools. Choosing the correct one depends on the implementation of the web server contained in the
    InteractiveTool and can be a bit tricky to get correct. In some cases, none of these options will work. One solution can then
    be to configure another highly customized proxy web server within the InteractiveTool, e.g. using NGINX.
@@ -41,7 +41,7 @@ is not available already.
 Automatic build of Linux containers
 -----------------------------------

-We utilize mulled_ with involucro_ to automatically convert all packages in Bioconda_ into Linux containers images 
+We utilize mulled_ with involucro_ to automatically convert all packages in Bioconda_ into Linux container images 
 (Docker and rkt at the moment) and make them available at the `BioContainers Quay.io account`_.

 We have developed small utilities around this technology stack, which is currently included in the ``galaxy-tool-util``
@@ -122,7 +122,7 @@ Build, test, and push a conda-forge package to biocontainers
 > You need to have write access to the biocontainers repository

 You can build packages from other Conda channels as well, not only from BioConda. ``pandoc`` tool is available from the
-conda-forge channel and conda-forge is also enabled by default in Galaxy. To build ``pandoc`` and push it to biocontainrs
+conda-forge channel and conda-forge is also enabled by default in Galaxy. To build ``pandoc`` and push it to biocontainers
 you could do something along these lines.


@@ -167,7 +167,7 @@ In order to generate the list file the ``mulled-list`` command may be useful. Th

   $ mulled-list --source docker --not-singularity --blacklist blacklist.txt --file output.txt

-The list of containers will be saved as ``output.txt``. The (optional) ``--blacklist`` option may be used to exclude containers which should not included in the output; ``blacklist.txt`` should contain a list of the 'blacklisted' containers, each on a new line.
+The list of containers will be saved as ``output.txt``. The (optional) ``--blacklist`` option may be used to exclude containers which should not be included in the output; ``blacklist.txt`` should contain a list of the 'blacklisted' containers, each on a new line.

 The generated containers should also be tested. This can be achieved by affixing ``--testing test-output.log`` to the ``mulled-update-singularity-containers`` command:

@@ -5,7 +5,7 @@ Tiny plugin interface to extend the Galaxy client.

 Galaxy webhooks provides a simple way of inserting icons, links, or other HTML elements into predefined locations.
 For this Galaxy provides some entry points which can be used to extend the client with content. This content
-can consists out of simple HTML, JS or dynamically generated content from a python function.
+can consist of simple HTML, JS or dynamically generated content from a python function.

  Please note that the webhooks interface is new and can change in the coming releases. Consider it as beta as we don't
  make promises to keep the API stable at the moment.
@@ -82,7 +82,7 @@ The configuration file is just a .yml (or .yaml) file with a few options. The fo
 - **activate** - *true* or *false* - whether show the plugin on a page or not
 - **icon** Icon to show (if masthead)
 - **tooltip** - Tooltip to show on hover
- **function** - A javascript function to be executed. Any calls to Galaxy APIs should be sure to use Galaxy.root when constructing the URL to ensure compatability across Galaxy deployments.
+- **function** - A javascript function to be executed. Any calls to Galaxy APIs should be sure to use Galaxy.root when constructing the URL to ensure compatibility across Galaxy deployments.

 All other options can be anything used by the plugin and accessed later via *webhook.config['...']*.

@@ -88,7 +88,7 @@ These tools can also be exported to disk and loaded like regular tools, enabling

 ## Security considerations

-User-defined tools share the same security risks as interactive tools..
+User-defined tools share the same security risks as interactive tools.
 See https://training.galaxyproject.org/training-material/topics/admin/tutorials/interactive-tools/tutorial.html#securing-interactive-tools for an extended discussion,
 and see https://github.com/galaxyproject/galaxy/blob/dev/test/integration/embedded_pulsar_job_conf.yml#L29 for a simple example that uses embedded pulsar to isolate mounts and disables network access.
 While the feature is in beta we recommend that only trusted users are allowed to use this feature.