Correct Typo in _docs/template-engines.md (#649)

I was recently reading through the documentation of the site when I noticed this typo. Just quickly popped into GitHub to open a correction via the web interface. Let me know if additional steps need to be taken to get this compliant with your PR process.

bridgetown-website/src/_docs/template-engines.md

@@ -5,7 +5,7 @@ top_section: Designing Your Site
 category: template-engines
 ---
 
-Bridgetown's default configured template language is **Liquid**. Liquid's simple syntax and safe execution context making it ideal for designer-led template creation.
+Bridgetown's default configured template language is **Liquid**. Liquid's simple syntax and safe execution context make it ideal for designer-led template creation.
 
 However, you can use a variety of different template engines within Bridgetown simply by using the appropriate file extension (aka `.erb`), or by specifying the template engine in your resource's front matter. Out of the box, Bridgetown provides support for both **ERB** and **Serbea**, and you can also use Haml or Slim by installing additional plugins.
 
@@ -60,4 +60,4 @@ It's worth noting that by combining Markdown, ERB/Serbea, components, and fronte
 
 ## It's Up to You
 
-Regardless of which template engine you pick, whether it's [Liquid](/docs/template-engines/liquid), [ERB, Serbea](/docs/template-engines/erb-and-beyond), or something else, Bridgetown has got you covered. We continue to look for ways to make switching engines easier while reducing the number of "sharp edges" that can arise to differences in how various template engines process content, so please don't hesitate to [let us know](/community) if you run in to any issues.
+Regardless of which template engine you pick, whether it's [Liquid](/docs/template-engines/liquid), [ERB, Serbea](/docs/template-engines/erb-and-beyond), or something else, Bridgetown has got you covered. We continue to look for ways to make switching engines easier while reducing the number of "sharp edges" that can arise to differences in how various template engines process content, so please don't hesitate to [let us know](/community) if you run in to any issues.