From 34f19646258b1fa49220b4e3829442f9a129d453 Mon Sep 17 00:00:00 2001 From: Anton Nekrutenko Date: Wed, 18 Jul 2007 20:35:03 +0000 Subject: [PATCH] Fixing typos --- tools/extract/interval2maf.xml | 2 +- tools/extract/interval_maf_to_merged_fasta.xml | 2 +- tools/extract/interval_maf_to_merged_fasta_user.xml | 2 +- tools/extract/user_interval2maf.xml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tools/extract/interval2maf.xml b/tools/extract/interval2maf.xml index 74bdad486c0..a37025e1319 100644 --- a/tools/extract/interval2maf.xml +++ b/tools/extract/interval2maf.xml @@ -26,7 +26,7 @@ What is the differences between these two tools: **Extract MAF blocks from locally cached alignments** and **Extract MAF blocks from user supplied alignments**? * **Extract MAF blocks from locally cached alignments** uses alignments stored at Galaxy installation at Penn State and is appropriate for most situations. It takes only one dataset as the input - a list of genomic intervals. - * **Extract MAF blocks from user supplied alignments** allows the user to work with his/her own alignemnts instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignemnts. + * **Extract MAF blocks from user supplied alignments** allows the user to work with his/her own alignments instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignments. ----- diff --git a/tools/extract/interval_maf_to_merged_fasta.xml b/tools/extract/interval_maf_to_merged_fasta.xml index df757eecf59..31d8e58b7d4 100644 --- a/tools/extract/interval_maf_to_merged_fasta.xml +++ b/tools/extract/interval_maf_to_merged_fasta.xml @@ -35,7 +35,7 @@ What is the differences between these two tools: **Stitch MAF blocks for intervals using locally cached alignments** and **Stitch MAF blocks for intervals from user supplied alignments**? * **Stitch MAF blocks for intervals using locally cached alignments** uses alignments stored at Galaxy installation at Penn State and is appropriate for most situations. It takes only one dataset as the input - a list of genomic intervals. - * **Stitch MAF blocks for intervals from user supplied alignments** allows the user to work with his/her own alignemnts instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignemnts. + * **Stitch MAF blocks for intervals from user supplied alignments** allows the user to work with his/her own alignments instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignments. In the future these two tools will be merged. diff --git a/tools/extract/interval_maf_to_merged_fasta_user.xml b/tools/extract/interval_maf_to_merged_fasta_user.xml index f5ad85be6c1..acbf05907e5 100644 --- a/tools/extract/interval_maf_to_merged_fasta_user.xml +++ b/tools/extract/interval_maf_to_merged_fasta_user.xml @@ -33,7 +33,7 @@ What is the differences between these two tools: **Stitch MAF blocks for intervals using locally cached alignments** and **Stitch MAF blocks for intervals from user supplied alignments**? * **Stitch MAF blocks for intervals using locally cached alignments** uses alignments stored at Galaxy installation at Penn State and is appropriate for most situations. It takes only one dataset as the input - a list of genomic intervals. - * **Stitch MAF blocks for intervals from user supplied alignments** allows the user to work with his/her own alignemnts instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignemnts. + * **Stitch MAF blocks for intervals from user supplied alignments** allows the user to work with his/her own alignments instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignments. In the future these two tools will be merged. diff --git a/tools/extract/user_interval2maf.xml b/tools/extract/user_interval2maf.xml index 2c6f4a6094b..8b6cef4ce73 100644 --- a/tools/extract/user_interval2maf.xml +++ b/tools/extract/user_interval2maf.xml @@ -17,7 +17,7 @@ What is the differences between these two tools: **Extract MAF blocks from locally cached alignments** and **Extract MAF blocks from user supplied alignments**? * **Extract MAF blocks from locally cached alignments** uses alignments stored at Galaxy installation at Penn State and is appropriate for most situations. It takes only one dataset as the input - a list of genomic intervals. - * **Extract MAF blocks from user supplied alignments** allows the user to work with his/her own alignemnts instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignemnts. + * **Extract MAF blocks from user supplied alignments** allows the user to work with his/her own alignments instead of those cached at Galaxy site. This tool takes two datasets as inputs - (1) genomic intervals and (2) alignments. -----