README.md in knapsack_pro-0.57.0 vs README.md in knapsack_pro-1.0.0

@@ -164,10 +164,11 @@
     - [How is that data secured?](#how-is-that-data-secured)
     - [Who has access to the data?](#who-has-access-to-the-data)
 - [Gem tests](#gem-tests)
   - [Spec](#spec)
 - [Contributing](#contributing)
+  - [Publishing](#publishing)
 - [Mentions](#mentions)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
 ## Update gem
@@ -771,11 +772,11 @@
 end
 ```
 
 #### Info for Travis users
 
-You can parallelize your builds across virtual machines with [travis matrix feature](http://docs.travis-ci.com/user/speeding-up-the-build/#Parallelizing-your-builds-across-virtual-machines). Edit `.travis.yml`
+You can parallelize your builds across virtual machines with [travis matrix feature](http://docs.travis-ci.com/user/speeding-up-the-build/#parallelizing-your-builds-across-virtual-machines). Edit `.travis.yml`
 
 ```yaml
 script:
   # Step for RSpec
   - "bundle exec rake knapsack_pro:rspec"
@@ -810,11 +811,11 @@
 Such configuration will generate matrix with 2 following ENV rows:
 
     KNAPSACK_PRO_CI_NODE_TOTAL=2 KNAPSACK_PRO_CI_NODE_INDEX=0 KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC=rspec-token KNAPSACK_PRO_TEST_SUITE_TOKEN_CUCUMBER=cucumber-token KNAPSACK_PRO_TEST_SUITE_TOKEN_MINITEST=minitest-token KNAPSACK_PRO_TEST_SUITE_TOKEN_TEST_UNIT=test-unit-token KNAPSACK_PRO_TEST_SUITE_TOKEN_SPINACH=spinach-token
     KNAPSACK_PRO_CI_NODE_TOTAL=2 KNAPSACK_PRO_CI_NODE_INDEX=1 KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC=rspec-token KNAPSACK_PRO_TEST_SUITE_TOKEN_CUCUMBER=cucumber-token KNAPSACK_PRO_TEST_SUITE_TOKEN_MINITEST=minitest-token KNAPSACK_PRO_TEST_SUITE_TOKEN_TEST_UNIT=test-unit-token KNAPSACK_PRO_TEST_SUITE_TOKEN_SPINACH=spinach-token
 
-More info about global and matrix ENV configuration in [travis docs](https://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix).
+More info about global and matrix ENV configuration in [travis docs](https://docs.travis-ci.com/user/customizing-the-build/#build-matrix).
 
 #### Info for semaphoreapp.com users
 
 Knapsack Pro supports semaphoreapp ENVs `SEMAPHORE_THREAD_COUNT` and `SEMAPHORE_CURRENT_THREAD`. The only thing you need to do is set up knapsack_pro rspec/cucumber/minitest/test_unit command for as many threads as you need. Here is an example:
 
@@ -1942,9 +1943,32 @@
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. You can create example tests in related repository with example of [rails application and knapsack_pro gem usage](https://github.com/KnapsackPro/rails-app-with-knapsack_pro).
 6. Create a new Pull Request
+
+### Publishing
+
+Update version in `lib/knapsack_pro/version.rb` and `CHANGELOG.md`:
+
+```
+$ git commit -m "Bump version X.X.X"
+$ git push origin master
+```
+
+Create git tag for release:
+
+```
+$ git tag -a vX.X.X -m "Release vX.X.X"
+$ git push --tags
+```
+
+Build gem and publish it to RubyGems.org:
+
+```
+$ gem build knapsack_pro.gemspec
+$ gem push knapsack_pro-X.X.X.gem
+```
 
 ## Mentions
 
 List of articles where people mentioned Knapsack Pro: