Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Updated language flow, typos, and syntax.

  • Loading branch information...
commit dbbc0b6ac64bf02b6fdd631fe784f82fccc73c7d 1 parent a25d8ce
D. Deryl Downey authored

Showing 1 changed file with 18 additions and 18 deletions. Show diff stats Hide diff stats

  1. 36  content/integration/bundler.haml
36  content/integration/bundler.haml
@@ -4,18 +4,18 @@
4 4
 
5 5
 %p
6 6
   There is no need to do anything to make bundler work with RVM, but there
7  
-  is one thing about bundler that makes it harder to use - by default bundler
8  
-  does not generate wrappers for gem binaries. To use proper version of gem
9  
-  binary users a forced to prefix every command with `bundle exec` this makes
10  
-  working in console rather painful. Fortunately there are solutions that
11  
-  allow to just write binary names - and binary from gem specified in Gemfile
12  
-  will be used.
  7
+  is one thing about bundler that makes it harder to use. By default, bundler
  8
+  does not generate wrappers for gem binaries. To make use of the proper version 
  9
+  of a gem binary, users are forced to prefix every command with `bundle exec`.
  10
+  This makes working in the console rather painful. Fortunately, there are solutions 
  11
+  that allow us to just write binary names; the binary from 'gem' specified in the
  12
+  Gemfile will be used.
13 13
 
14 14
 %h2 RVM hook
15 15
 
16 16
 %p
17  
-  Thanks to Rick DeNatale we have now a hook that automatically will append
18  
-  BUNDLE_BIN path to PATH when changing directories.
  17
+  Thanks to Rick DeNatale, we now have a hook that automatically will append
  18
+  BUNDLE_BIN path to the PATH when changing directories.
19 19
 
20 20
 %p
21 21
   Enabling hook
@@ -32,16 +32,16 @@
32 32
       bundle install --binstubs=./bundler_stubs
33 33
 
34 34
 %p
35  
-  From now any project which was generated this way will automatically
  35
+  From now on, any project which was generated this way will automatically
36 36
   add ./bundler_stubs to the PATH.
37 37
 
38 38
 %h2 rubygems-bundler gem
39 39
 
40 40
 %p
41  
-  Another solution for this problem is gem which makes bundler and rubygems
42  
-  generate binaries wrappers that are aware of bundler, it was discussed with
43  
-  rubygems and bundler teams, as they did not really like the solution be
44  
-  warned they will most likely not support it.
  41
+  Another solution for this problem is a gem which makes bundler and rubygems
  42
+  generate binary wrappers that are aware of bundler. It was discussed with
  43
+  the rubygems and bundler teams, however,they did not really like the solution.
  44
+  Be forewarned, they will most likely not support it.
45 45
 
46 46
 %p
47 47
   Installation:
@@ -55,22 +55,22 @@
55 55
     rubygems-bundler @ github
56 56
 
57 57
 %p
58  
-  To make it fully working bundler 1.1 is required (which is not yet released),
59  
-  but fortunately the rubygems plugins enabled bundler is also available for
  58
+  To make it fully working, bundler 1.1 is required (which is not yet released).
  59
+  Fortunately, the rubygems plugins enabled bundler is also available for
60 60
   installation:
61 61
   %pre.code
62 62
     :preserve
63 63
       gem install mpapis-bundler
64 64
 
65 65
 %p
66  
-  As `mpapis-bundler` already depends on `rubygems-bundler` you could skip
  66
+  As `mpapis-bundler` already depends on `rubygems-bundler` you could skip the
67 67
   previous step. `mpapis-bundler` uses only code that is already in the commit
68  
-  tree of bundler - so you do not have to worry about compatibility.
  68
+  tree of bundler, so you do not have to worry about compatibility.
69 69
 
70 70
 %h2
71 71
   Community Resources
72 72
 %ul
73 73
   %li
74  
-    You can read bundler's README on
  74
+    You can read bundler's README at
75 75
     %a{:href => "http://github.com/carlhuda/bundler"}
76 76
       GitHub

0 notes on commit dbbc0b6

Please sign in to comment.
Something went wrong with that request. Please try again.