Merge pull request #6436 from Marie59/review

shiltemann · web-flow · commit 2207845fb4f6 · 2025-10-28T15:14:42.000+01:00
Review community tuto
diff --git a/topics/community/tutorials/community-lab/tutorial.md b/topics/community/tutorials/community-lab/tutorial.md
@@ -30,7 +30,7 @@ The **Community lab**, a centralised webpage that enables communities to rapidly
   *For example, [the microgalaxy lab (Europe)](https://microbiology.usegalaxy.eu).*
 
 
-The aim is this tutorial is to create the files necessary to display the labs in each Galaxy instance.
+The aim of this tutorial is to create the files necessary to display the labs in each Galaxy instance.
 
 You can also use the [Galaxy Labs engine](https://labs.usegalaxy.org.au).
 
@@ -76,7 +76,7 @@ communities/<your community>/lab/sections_templates/
 >
 > 1. Go to the [Galaxy Codex repo](https://github.com/galaxyproject/galaxy_codex)
 > 2. Go to the file `.github/workflows/populate_labs.yaml`
-> 3. On the right, click on the pen to "dit this file"
+> 3. On the right, click on the pen to "Edit this file"
 > 4. Duplicate section called "Populate biodiversity Lab"
 >
 >    For example:
@@ -105,7 +105,7 @@ communities/<your community>/lab/sections_templates/
 >
 > 1. Fork and clone the [Galaxy Codex repo](https://github.com/galaxyproject/galaxy_codex)
 > 2. Set the `COMMUNITY` variable : `export $COMMUNITY=<your community>`
-> 3. Lauch `sources/bin/populate_labs.sh`
+> 3. Launch `sources/bin/populate_labs.sh`
 >
 > This will create a bunch of the new files in the appropriate community folder (communities/<your community>/lab/).
 {: .hands_on}
diff --git a/topics/community/tutorials/community-tool-table/tutorial.md b/topics/community/tutorials/community-tool-table/tutorial.md
@@ -47,7 +47,7 @@ The generated community-specific table can be used as is (e.g. downloadable tsv
 
 The pipeline is **fully automated** and executes on a **weekly** basis. Any research community can apply the pipeline to create a table specific to their community.
 
-The aim is this tutorial is to create such table for a community.
+The aim of this tutorial is to create such table for a community.
 
 > <agenda-title></agenda-title>
 >
@@ -96,7 +96,7 @@ You will then be able to remove tools that are not relevant to your community or
 # Add the list relevant tags for your community in the categories file
 
 > <hands-on-title>Add the ToolShed catgories to the categories file</hands-on-title>
-> 1. Open or create the file named `categories` in your comunity metadata folder (`communities/<your community>/metadata/categories`)
+> 1. Open or create the file named `categories` in your community metadata folder (`communities/<your community>/metadata/categories`)
 > 2. Add the name of the categories relevant to your community in the `categories` file you started above, with 1 ToolShed category per row. For example, see [a list of valid ToolShed categories](https://toolshed.g2.bx.psu.edu/).
 >
 >    For example:
diff --git a/topics/community/tutorials/community-tutorial-table/tutorial.md b/topics/community/tutorials/community-tutorial-table/tutorial.md
@@ -33,9 +33,9 @@ The pipeline creates a table with all the tutorials. This table can be **filtere
 
 The generated community-specific table can be used as is (e.g. downloadable tsv file) and/or embedded (e.g. into a Galaxy Hub page or Galaxy subdomain). 
 
-The pipeline is **fully automated** and executes on a **weekly** basis. Any research community can apply the pipeline to create a table specific to their community.
+The pipeline is **fully automated** and executed on a **weekly** basis. Any research community can apply the pipeline to create a table specific to their community.
 
-The aim is this tutorial is to create a tutorial table for a community.
+The aim of this tutorial is to create a tutorial table for a community.
 
 > <agenda-title></agenda-title>
 >
@@ -86,7 +86,7 @@ You will then be able to remove tutorials that are not relevant to your communit
 # Add the list relevant tags for your community in the `tutorial_tags` file
 
 > <hands-on-title>Add the relevant tags to the tutorial_tags file</hands-on-title>
-> 1. Open or create a file named `tutorial_tags` in your comunity metadata folder (`communities/<your community>/metadata/tutorial_tags`)
+> 1. Open or create a file named `tutorial_tags` in your community metadata folder (`communities/<your community>/metadata/tutorial_tags`)
 > 2. Add the name of the tags relevant to your community in the `tutorial_tags` file, with 1 tag per row
 > (See above for how to identify the appropriate tags)
 >
diff --git a/topics/community/tutorials/community-workflow-table/tutorial.md b/topics/community/tutorials/community-workflow-table/tutorial.md
@@ -33,9 +33,9 @@ The pipeline creates a table with all the workflows associated to selected tags.
 
 The generated community-specific table can be used as it and/or embedded, e.g. into the respective Galaxy Hub page or Galaxy subdomain.
 
-The pipeline is **fully automated** and executes on a **weekly** basis. Any research community can apply the pipeline to create a table specific to their community.
+The pipeline is **fully automated** and executed on a **weekly** basis. Any research community can apply the pipeline to create a table specific to their community.
 
-The aim is this tutorial is to create a workflow table for a community.
+The aim of this tutorial is to create a workflow table for a community.
 
 > <agenda-title></agenda-title>
 >
@@ -78,22 +78,22 @@ You will then be able to remove workflows that are not relevant to your communit
 > 1. Go to your favorite public Galaxy instance.
 > 2. Go to the `Workflow` section
 > 3. Select `Public workflows` (for example: [Public workflows on the French instance](https://usegalaxy.fr/workflows/list_published))
-> 4. Browse for workflow that are releavnt to your community
+> 4. Browse for workflows that are relevant to your community
 > 5. Note the tags that are associated with workflows of interest
 {: .hands_on}
 
 > <hands-on-title>Select workflows tags from the Workflow Hub</hands-on-title>
 >
 > 1. Go to [Workflow Hub](https://workflowhub.eu/)
-> 2. Browse for workflow that are releavnt to your community
+> 2. Browse for workflows that are relevant to your community
 > 3. Note the tags that are associated with workflows of interest (in the `tag` section on the left of the workflow page)
 {: .hands_on}
 
 # Add the list relevant tags for your community in the workflow_tags file
 
 > <hands-on-title>Add the relevant tags to the workflow_tags file</hands-on-title>
 > 1. Open or create a file named `workflow_tags` in your comunity metadata folder (`communities/<your community>/metadata/workflow_tags`)
-> 2. Add the name of the tags relevant to your community in the `workflow_tags` file you started above. The file is split in two sections : `Public`, which should inidcate the tags used on public Galaxy instances; and `workflowhub`, which inidcates the tags to use to select workflow on [Workflow Hub](https://workflowhub.eu/).
+> 2. Add the name of the tags relevant to your community in the `workflow_tags` file you started above. The file is split in two sections : `Public`, which should inidcate the tags used on public Galaxy instances; and `workflowhub`, which indicates the tags to use to select workflow on [Workflow Hub](https://workflowhub.eu/).
 >
 >    For example:
 >    ```

Original file line number	Diff line number	Diff line change
`@@ -30,7 +30,7 @@ The Community lab, a centralised webpage that enables communities to rapidly`
`30`	`30`	`For example, [the microgalaxy lab (Europe)](https://microbiology.usegalaxy.eu).`
`31`	`31`
`32`	`32`
`33`		`-The aim is this tutorial is to create the files necessary to display the labs in each Galaxy instance.`
	`33`	`+The aim of this tutorial is to create the files necessary to display the labs in each Galaxy instance.`
`34`	`34`
`35`	`35`	`You can also use the [Galaxy Labs engine](https://labs.usegalaxy.org.au).`
`36`	`36`
`@@ -76,7 +76,7 @@ communities/<your community>/lab/sections_templates/`
`76`	`76`	`>`
`77`	`77`	`> 1. Go to the [Galaxy Codex repo](https://github.com/galaxyproject/galaxy_codex)`
`78`	`78`	> 2. Go to the file `.github/workflows/populate_labs.yaml`
`79`		`-> 3. On the right, click on the pen to "dit this file"`
	`79`	`+> 3. On the right, click on the pen to "Edit this file"`
`80`	`80`	`> 4. Duplicate section called "Populate biodiversity Lab"`
`81`	`81`	`>`
`82`	`82`	`> For example:`
`@@ -105,7 +105,7 @@ communities/<your community>/lab/sections_templates/`
`105`	`105`	`>`
`106`	`106`	`> 1. Fork and clone the [Galaxy Codex repo](https://github.com/galaxyproject/galaxy_codex)`
`107`	`107`	> 2. Set the `COMMUNITY` variable : `export $COMMUNITY=<your community>`
`108`		-> 3. Lauch `sources/bin/populate_labs.sh`
	`108`	+> 3. Launch `sources/bin/populate_labs.sh`
`109`	`109`	`>`
`110`	`110`	`> This will create a bunch of the new files in the appropriate community folder (communities/<your community>/lab/).`
`111`	`111`	`{: .hands_on}`
Original file line number	Diff line number	Diff line change
`@@ -47,7 +47,7 @@ The generated community-specific table can be used as is (e.g. downloadable tsv`
`47`	`47`
`48`	`48`	`The pipeline is fully automated and executes on a weekly basis. Any research community can apply the pipeline to create a table specific to their community.`
`49`	`49`
`50`		`-The aim is this tutorial is to create such table for a community.`
	`50`	`+The aim of this tutorial is to create such table for a community.`
`51`	`51`
`52`	`52`	`> <agenda-title></agenda-title>`
`53`	`53`	`>`
`@@ -96,7 +96,7 @@ You will then be able to remove tools that are not relevant to your community or`
`96`	`96`	`# Add the list relevant tags for your community in the categories file`
`97`	`97`
`98`	`98`	`> <hands-on-title>Add the ToolShed catgories to the categories file</hands-on-title>`
`99`		-> 1. Open or create the file named `categories` in your comunity metadata folder (`communities/<your community>/metadata/categories`)
	`99`	+> 1. Open or create the file named `categories` in your community metadata folder (`communities/<your community>/metadata/categories`)
`100`	`100`	> 2. Add the name of the categories relevant to your community in the `categories` file you started above, with 1 ToolShed category per row. For example, see [a list of valid ToolShed categories](https://toolshed.g2.bx.psu.edu/).
`101`	`101`	`>`
`102`	`102`	`> For example:`