Merge pull request #26 from inecho/pull-request

Update on Gemfile

Gemfile

@@ -1,9 +1,9 @@
 source 'https://rubygems.org'
 
-gem 'jekyll', '~> 3.1.0'
+gem 'jekyll', '~> 3.8.3'
 gem 'coderay', '~> 1.1.0'
 gem 'rake-jekyll', '~> 1.1.0'
 
 group :jekyll_plugins do
- gem 'jekyll-asciidoc', '~> 2.0.1'
+ gem 'jekyll-asciidoc', '~> 2.1.0'
 end

README.adoc

@@ -88,6 +88,8 @@ If you can load the `[username].github.io/jekyll-asciidoc-quickstart` home page,
 
 Start writing blog posts and enjoy the AsciiDoc difference, regardless of what device you choose: computer, tablet, or mobile.
 
+If would you like to work offline first, consider to check your `Gemfile` for the versions of your gem sources. As the case may be, your `jekyll serve` will fail. So make sure to check your gem sources with `gem list --local | grep "jekyll"`.
+
 = Details
 
 == GitHub Pages and AsciiDoc

index.adoc

@@ -11,7 +11,7 @@ Now that you've set up your website to run with AsciiDoc, you have a ton of opti
 
 === Edit content
 
-Editing content is very simple. The easiest way to update your blog is to clone your repository, fire up your favorite text editor and run the content locally. To do this run the `jekyll serve` command and open a web browser to http:https://localhost:4000. Jekyll will automatically process and host changes to the content.
+Editing content is very simple. The easiest way to update your blog is to clone your repository, fire up your favorite text editor and run the content locally. To do this run the `jekyll serve` command and open a web browser to http:https://localhost:4000. Jekyll will automatically process and host changes to the content. Also make sure that your `Gemfile` is up-to-date with the current version of your gem sources, e.g. with `gem list --local | grep "jekyll"`.
 
 You may also edit your content directly on Github. To do this, navigate the browser the file you wish to edit, click the pensil (edit) button in the upper right hand corner of the view and make your changes. When you're finished, commit your changes. This will trigger Travis to generate and publish a new website including your changes.