typos fixed, thanks to @gbezyuk

chrisvfritz · chrisvfritz · commit a1b60e7cf023 · 2016-11-14T23:52:35.000-05:00
diff --git a/src/v2/guide/render-function.md b/src/v2/guide/render-function.md
@@ -6,7 +6,7 @@ order: 15
 
 ## Basics
 
-Vue recommends using templates to build your HTML in the vast majority of cases. There are situations however, where you really need the full programmatic power of JavaScript. That's where you can use the **render  function**, a closer-to-the-compiler alternative to templates.
+Vue recommends using templates to build your HTML in the vast majority of cases. There are situations however, where you really need the full programmatic power of JavaScript. That's where you can use the **render function**, a closer-to-the-compiler alternative to templates.
 
 Let's dive into a simple example where a `render` function would be practical. Say you want to generate anchored headings:
 
diff --git a/src/v2/guide/single-file-components.md b/src/v2/guide/single-file-components.md
@@ -6,7 +6,7 @@ order: 19
 
 ## Introduction
 
-In many Vue projects, global components will be defined using `Vue.component`, followed by `new Vue({ el: '#container '})` to target a container element in the body of every page.
+In many Vue projects, global components will be defined using `Vue.component`, followed by `new Vue({ el: '#container' })` to target a container element in the body of every page.
 
 This can work very well for small to medium-sized projects, where JavaScript is only used to enhance certain views. In more complex projects however, or when your frontend is entirely driven by JavaScript, these disadvantages become apparent:
 
