fix parsing error

_posts/core-samples/2011-12-29-jekyll-introduction.md

@@ -9,7 +9,7 @@ tags : [intro, beginner, jekyll, tutorial]
 This Jekyll introduction will outline specifically  what Jekyll is and why you would want to use it.
 Directly following the intro we'll learn exactly _how_ Jekyll does what it does.
 
-## Overview 
+## Overview
 
 ### What is Jekyll?
 
@@ -26,7 +26,7 @@ This website is created with Jekyll. [Other Jekyll websites](https://github.com/
 
 Jekyll is a ruby gem you install on your local system.
 Once there you can call `jekyll --server` on a directory and provided that directory
-is setup in a way jekyll expects, it will do magic stuff like parse markdown/textile files, 
+is setup in a way jekyll expects, it will do magic stuff like parse markdown/textile files,
 compute categories, tags, permalinks, and construct your pages from layout templates and partials.
 
 Once parsed, Jekyll stores the result in a self-contained static `_site` folder.
@@ -70,7 +70,7 @@ Be aware that core concepts are introduced in rapid succession without code exam
 This information is not intended to specifically teach you how to do anything, rather it
 is intended to give you the _full picture_ relative to what is going on in Jekyll-world.
 
-Learning these core concepts should help you avoid common frustrations and ultimately 
+Learning these core concepts should help you avoid common frustrations and ultimately
 help you better understand the code examples contained throughout Jekyll-Bootstrap.
 
 
@@ -100,24 +100,24 @@ Jekyll expects your website directory to be laid out like so:
         |-- javascripts
 
 
-- **\_config.yml**  
+- **\_config.yml**
 	Stores configuration data.
 
-- **\_includes**  
+- **\_includes**
 	This folder is for partial views.
 
-- **\_layouts**   
+- **\_layouts**
 	This folder is for the main templates your content will be inserted into.
 	You can have different layouts for different pages or page sections.
 
-- **\_posts**  
+- **\_posts**
 	This folder contains your dynamic content/posts.
 	the naming format is required to be `@YEAR-MONTH-DATE-title.MARKUP@`.
 
-- **\_site**  
-	This is where the generated site will be placed once Jekyll is done transforming it. 
+- **\_site**
+	This is where the generated site will be placed once Jekyll is done transforming it.
 
-- **assets**  
+- **assets**
 	This folder is not part of the standard jekyll structure.
 	The assets folder represents _any generic_ folder you happen to create in your root directory.
 	Directories and files not properly formatted for jekyll will be left untouched for you to serve normally.
@@ -128,7 +128,7 @@ Jekyll expects your website directory to be laid out like so:
 ### Jekyll Configuration
 
 Jekyll supports various configuration options that are fully outlined here:
-<https://github.com/mojombo/jekyll/wiki/Configuration>
+(<https://github.com/mojombo/jekyll/wiki/Configuration>)
 
 
 
@@ -145,27 +145,27 @@ Both posts and pages can have meta-data assigned on a per-page basis such as tit
 
 ### Working With Posts
 
-**Creating a Post**   
+**Creating a Post**
 Posts are created by properly formatting a file and placing it the `_posts` folder.
 
-**Formatting**  
-A post must have a valid filename in the form `YEAR-MONTH-DATE-title.MARKUP` and be placed in the `_posts` directory. 
+**Formatting**
+A post must have a valid filename in the form `YEAR-MONTH-DATE-title.MARKUP` and be placed in the `_posts` directory.
 If the data format is invalid Jekyll will not recognize the file as a post. The date and title are automatically parsed from the filename of the post file.
 Additionally, each file must have [YAML Front-Matter](https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter) prepended to its content.
 YAML Front-Matter is a valid YAML syntax specifying meta-data for the given file.
 
-**Order**  
+**Order**
 Ordering is an important part of Jekyll but it is hard to specify a custom ordering strategy.
 Only reverse chronological and chronological ordering is supported in Jekyll.
 
 Since the date is hard-coded into the filename format, to change the order, you must change the dates in the filenames.
 
-**Tags**   
+**Tags**
 Posts can have tags associated with them as part of their meta-data.
 Tags may be placed on posts by providing them in the post's YAML front matter.
 You have access to the post-specific tags in the templates. These tags also get added to the sitewide collection.
 
-**Categories**   
+**Categories**
 Posts may be categorized by providing one or more categories in the YAML front matter.
 Categories offer more significance over tags in that they can be reflected in the URL path to the given post.
 Note categories in Jekyll work in a specific way.
@@ -182,17 +182,17 @@ You won't find "lessons" and "beginner" as two separate categories unless you de
 
 ### Working With Pages
 
-**Creating a Page**  
+**Creating a Page**
 Pages are created by properly formatting a file and placing it anywhere in the root directory or subdirectories that do _not_ start with an underscore.
 
-**Formatting**  
+**Formatting**
 In order to register as a Jekyll page the file must contain [YAML Front-Matter](https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter).
 Registering a page means 1) that Jekyll will process the page and 2) that the page object will be available in the `site.pages` array for inclusion into your templates.
 
-**Categories and Tags**  
+**Categories and Tags**
 Pages do not compute categories nor tags so defining them will have no effect.
 
-**Sub-Directories**  
+**Sub-Directories**
 If pages are defined in sub-directories, the path to the page will be reflected in the url.
 Example:
 
@@ -204,15 +204,15 @@ Example:
 This page will be available at `http://yourdomain.com/people/bob/essay.html`
 
 
-**Recommended Pages**  
+**Recommended Pages**
 
-- **index.html**  
+- **index.html**
   You will always want to define the root index.html page as this will display on your root URL.
-- **404.html**  
+- **404.html**
   Create a root 404.html page and GitHub Pages will serve it as your 404 response.
-- **sitemap.html**  
+- **sitemap.html**
   Generating a sitemap is good practice for SEO.
-- **about.html**  
+- **about.html**
   A nice about page is easy to do and gives the human perspective to your website.
 
 
@@ -223,14 +223,14 @@ All templates have access to a global site object variable: `site` as well as a
 The site variable holds all accessible content and metadata relative to the site.
 The page variable holds accessible data for the given page or post being rendered at that point.
 
-**Create a Template**  
+**Create a Template**
 Templates are created by properly formatting a file and placing it in the `_layouts` directory.
 
-**Formatting**  
-Templates should be coded in HTML and contain YAML Front Matter. 
+**Formatting**
+Templates should be coded in HTML and contain YAML Front Matter.
 All templates can contain Liquid code to work with your site's data.
 
-**Rending Page/Post Content in a Template**  
+**Rending Page/Post Content in a Template**
 There is a special variable in all templates named : `content`.
 The `content` variable holds the page/post content including any sub-template content previously defined.
 Render the content variable wherever you want your main content to be injected into your template:
@@ -247,7 +247,7 @@ Render the content variable wherever you want your main content to be injected i
 
 ### Sub-Templates
 
-Sub-templates are exactly templates with the only difference being they 
+Sub-templates are exactly templates with the only difference being they
 define another "root" layout/template within their YAML Front Matter.
 This essentially means a template will render inside of another template.
 
@@ -267,32 +267,32 @@ This is mainly due to the fact that Jekyll templates must use the Liquid Templat
 ### What is Liquid?
 
 [Liquid](https://github.com/Shopify/liquid) is a secure templating language developed by [Shopify](http://shopify.com).
-Liquid is designed for end-users to be able to execute logic within template files 
+Liquid is designed for end-users to be able to execute logic within template files
 without imposing any security risk on the hosting server.
 
 Jekyll uses Liquid to generate the post content within the final page layout structure and as the primary interface for working with
-your site and post/page data. 
+your site and post/page data.
 
 ### Why Do We Have to Use Liquid?
 
-GitHub uses Jekyll to power [GitHub Pages](http://pages.github.com/). 
+GitHub uses Jekyll to power [GitHub Pages](http://pages.github.com/).
 GitHub cannot afford to run arbitrary code on their servers so they lock developers down via Liquid.
 
 ### Liquid is Not Programmer-Friendly.
 
 The short story is liquid is not real code and its not intended to execute real code.
 The point being you can't do jackshit in liquid that hasn't been allowed explicitly by the implementation.
-What's more you can only access data-structures that have been explicitly passed to the template. 
+What's more you can only access data-structures that have been explicitly passed to the template.
 
-In Jekyll's case it is not possible to alter what is passed to Liquid without hacking the gem or running custom plugins. 
+In Jekyll's case it is not possible to alter what is passed to Liquid without hacking the gem or running custom plugins.
 Both of which cannot be supported by GitHub Pages.
 
 As a programmer - this is very frustrating.
 
-But rather than look a gift horse in the mouth we are going to 
+But rather than look a gift horse in the mouth we are going to
 suck it up and view it as an opportunity to work around limitations and adopt client-side solutions when possible.
 
-**Aside**   
+**Aside**
 My personal stance is to not invest time trying to hack liquid. It's really unnecessary
 _from a programmer's_ perspective. That is to say if you have the ability to run custom plugins (i.e. run arbitrary ruby code)
 you are better off sticking with ruby. Toward that end I've built [Mustache-with-Jekyll](http://github.com/plusjade/mustache-with-jekyll)
@@ -303,7 +303,7 @@ you are better off sticking with ruby. Toward that end I've built [Mustache-with
 Static assets are any file in the root or non-underscored subfolders that are not pages.
 That is they have no valid YAML Front Matter and are thus not treated as Jekyll Pages.
 
-Static assets should be used for images, css, and javascript files. 
+Static assets should be used for images, css, and javascript files.
 
 
 
@@ -312,21 +312,21 @@ Static assets should be used for images, css, and javascript files.
 
 Remember Jekyll is a processing engine. There are two main types of parsing in Jekyll.
 
-- **Content parsing.**   
+- **Content parsing.**
 	This is done with textile or markdown.
-- **Template parsing.**   
+- **Template parsing.**
   This is done with the liquid templating language.
 
 And thus there are two main types of file formats needed for this parsing.
 
-- **Post and Page files.**  
+- **Post and Page files.**
   All content in Jekyll is either a post or a page so valid posts and pages are parsed with markdown or textile.
-- **Template files.**    
+- **Template files.**
 	These files go in `_layouts` folder and contain your blogs **templates**. They should be made in HTML with the help of Liquid syntax.
 	Since include files are simply injected into templates they are essentially parsed as if they were native to the template.
 
-**Arbitrary files and folders.**   
-Files that _are not_ valid pages are treated as static content and pass through 
+**Arbitrary files and folders.**
+Files that _are not_ valid pages are treated as static content and pass through
 Jekyll untouched and reside on your blog in the exact structure and format they originally existed in.
 
 ### Formatting Files for Parsing.
@@ -363,30 +363,30 @@ That is to say loading a post file into a template file that refers to another t
 
 ## How Jekyll Generates the Final Static Files.
 
-Ultimately, Jekyll's job is to generate a static representation of your website. 
+Ultimately, Jekyll's job is to generate a static representation of your website.
 The following is an outline of how that's done:
 
-1. **Jekyll collects data.**   
+1. **Jekyll collects data.**
   Jekyll scans the posts directory and collects all posts files as post objects. It then scans the layout assets and collects those and finally scans other directories in search of pages.
 
-2. **Jekyll computes data.**   
-  Jekyll takes these objects, computes metadata (permalinks, tags, categories, titles, dates) from them and constructs one 
+2. **Jekyll computes data.**
+  Jekyll takes these objects, computes metadata (permalinks, tags, categories, titles, dates) from them and constructs one
   big `site` object that holds all the posts, pages, layouts, and respective metadata.
   At this stage your site is one big computed ruby object.
 
-3. **Jekyll liquifies posts and templates.**  
+3. **Jekyll liquifies posts and templates.**
   Next jekyll loops through each post file and converts (through markdown or textile) and **liquifies** the post inside of its respective layout(s).
-  Once the post is parsed and liquified inside the the proper layout structure, the layout itself is "liquified".   
+  Once the post is parsed and liquified inside the the proper layout structure, the layout itself is "liquified".
 	**Liquification** is defined as follows: Jekyll initiates a Liquid template, and passes a simpler hash representation of the ruby site object as well as a simpler
   hash representation of the ruby post object. These simplified data structures are what you have access to in the templates.
-	
-3. **Jekyll generates output.**   
+
+3. **Jekyll generates output.**
 	Finally the liquid templates are "rendered", thereby processing any liquid syntax provided in the templates
 	and saving the final, static representation of the file.
- 
-**Notes.**  
-Because Jekyll computes the entire site in one fell swoop, each template is given access to 
-a global `site` hash that contains useful data. It is this data that you'll iterate through and format 
+
+**Notes.**
+Because Jekyll computes the entire site in one fell swoop, each template is given access to
+a global `site` hash that contains useful data. It is this data that you'll iterate through and format
 using the Liquid tags and filters in order to render it onto a given page.
 
 Remember, in Jekyll you are an end-user. Your API has only two components:
@@ -408,5 +408,5 @@ Jekyll-bootstrap is intended to provide helper methods and strategies aimed at m
 
 ## Next Steps
 
-Please take a look at [{{ site.categories.api.first.title }}]({{ BASE_PATH }}{{ site.categories.api.first.url }}) 
+Please take a look at [{{ site.categories.api.first.title }}]({{ BASE_PATH }}{{ site.categories.api.first.url }})
 or jump right into [Usage]({{ BASE_PATH }}{{ site.categories.usage.first.url }}) if you'd like.