From 7d60b1a55ae7dc26a75a2b0cb82c80c39caa1e36 Mon Sep 17 00:00:00 2001
From: Ryan Watters <watters.ryan@gmail.com>
Date: Thu, 6 Apr 2017 15:46:23 -0500
Subject: [PATCH] Update mixed param type error for shortcodes

---
 content/templates/shortcode-templates.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/templates/shortcode-templates.md b/content/templates/shortcode-templates.md
index ce6c7d494..bdd03c00a 100644
--- a/content/templates/shortcode-templates.md
+++ b/content/templates/shortcode-templates.md
@@ -114,7 +114,7 @@ You could then include the following as part of your shortcode templating:
 See the [example Vimeo shortcode][vimeoexample] below for `.IsNamedParams` in action
 
 {{% warning %}}
-While you can create shortcode templates that accept both positional and named parameter, you *cannot* declare shortcodes in content with a mix of parameter types. Therefore, a shortcode declare like `{{</* image src="images/my-image.jpg" "This is my alt text" */>}}` will return an error.
+While you can create shortcode templates that accept both positional and named parameters, you *cannot* declare shortcodes in content with a mix of parameter types. A shortcode declared like `{{</* image src="images/my-image.jpg" "This is my alt text" */>}}` will return an error.
 {{% /warning %}}
 
 You can also use the variable `.Page` to access all the normal [page variables][pagevars].