# HG changeset patch
# User iuc
# Date 1589901941 0
# Node ID ceed4b724f0b158847dc29e0bf533e05e51f8763
# Parent  086ba7b646e5486bf3325524491f83a8a861a31f
"planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/bwa commit 777181bd04849dab271ee2cc95e45c182947d308"

diff -r 086ba7b646e5 -r ceed4b724f0b bwa_macros.xml
--- a/bwa_macros.xml	Thu Sep 05 19:35:56 2019 -0400
+++ b/bwa_macros.xml	Tue May 19 15:25:41 2020 +0000
@@ -114,8 +114,8 @@
 **Specify read group information?** widget. If you are not familiar with read groups you shold know that this is effectively a way to tag reads with an additional ID.
 This allows you to combine BAM files from, for example, multiple BWA runs into a single dataset. This significantly simplifies downstream processing as
 instead of dealing with multiple datasets you only have to handle only one. This is possible because the read group information allows you to identify
-data from different experiments even if they are combined in one file. Many downstream analysis tools such as varinat callers (e.g., FreeBayes or Naive Varinat Caller
-present in Galaxy) are aware of readgtroups and will automatically generate calls for each individual sample even if they are combined within a single file.
+data from different experiments even if they are combined in one file. Many downstream analysis tools such as variant callers (e.g., FreeBayes or Naive Variant Caller
+present in Galaxy) are aware of read groups and will automatically generate calls for each individual sample even if they are combined within a single file.
 
 **Description of read groups fields**