FAQ, manual: use the proper buzzwords for Ruby version managers. (@lloeki)

README.markdown

@@ -437,15 +437,15 @@ scripts.
 __4.12. Q. How can I check scripts written for different versions of Ruby?__
 
 A. Install a Ruby version manager such as [rvm][rvm] or [rbenv][rbenv],
-activate the environment for the relevant version of Ruby, and install in it
+activate the relevant version of Ruby, and install in it the checkers you want
-the checkers you want to use.  Set `g:syntastic_ruby_checkers` accordingly in
+to use.  Set `g:syntastic_ruby_checkers` accordingly in your `vimrc`, and run
-your `vimrc`, and run [Vim][vim] from the virtual environment.
+[Vim][vim] under the relevant Ruby version.
 
-If you're starting Vim from a desktop manager rather than from a terminal you
+If you're starting Vim from a desktop manager rather than from a terminal
-might need to write wrapper scripts around your checkers, to activate the
+and depending on the version manager you use you might need to write wrapper
-virtual environment before running the actual checks.  Then you'll need to
+scripts around your checkers, to activate the relevant version of Ruby
-point the relevant `g:syntastic_ruby_<checker>_exec` variables to the wrapper
+before running the actual checks.  Then you'll need to point the relevant
-scripts.
+`g:syntastic_ruby_<checker>_exec` variables to the wrapper scripts.
 
 <a name="faqperl"></a>
 

doc/syntastic-checkers.txt

@@ -5720,11 +5720,12 @@ running "rubocop --version" from the shell. If it complains about "Parser"
 "Ruby" than you are running, your configuration is not directly supported by
 syntastic.
 
-While passing around the blame for this does have a certain entertaining value
+While passing around the blame for this does have a certain entertaining
-(cf. https://github.com/bbatsov/rubocop/issues/1819), the problem is real,
+value (cf. https://github.com/bbatsov/rubocop/issues/1819), the problem
-since "Ruby" syntax did change between versions. The solution is to run a
+is real, since "Ruby" syntax did change between versions. The solution
-system such as "rbenv" (http://rbenv.org/) or "rvm" (https://rvm.io/), that
+is to run a version manager such as "rbenv" (http://rbenv.org/) or "rvm"
-allows you to run multiple versions of "Ruby" without conflicts: >
+(https://rvm.io/), that allows you to run multiple versions of "Ruby" without
+conflicts: >
     $ rbenv version
     2.1.3 (set by /usr/local/var/rbenv/version)
     
@@ -5768,11 +5769,12 @@ running "ruby-lint --version" from the shell. If it complains about "Parser"
 "Ruby" than you are running, your configuration is not directly supported by
 syntastic.
 
-While passing around the blame for this does have a certain entertaining value
+While passing around the blame for this does have a certain entertaining
-(cf. https://github.com/bbatsov/rubocop/issues/1819), the problem is real,
+value (cf. https://github.com/bbatsov/rubocop/issues/1819), the problem
-since "Ruby" syntax did change between versions. The solution is to run a
+is real, since "Ruby" syntax did change between versions. The solution
-system such as "rbenv" (http://rbenv.org/) or "rvm" (https://rvm.io/), that
+is to run a version manager such as "rbenv" (http://rbenv.org/) or "rvm"
-allows you to run multiple versions of "Ruby" without conflicts: >
+(https://rvm.io/), that allows you to run multiple versions of "Ruby" without
+conflicts: >
     $ rbenv version
     2.1.3 (set by /usr/local/var/rbenv/version)
     

plugin/syntastic.vim

@@ -19,7 +19,7 @@ if has('reltime')
     lockvar! g:_SYNTASTIC_START
 endif
 
-let g:_SYNTASTIC_VERSION = '3.8.0-63'
+let g:_SYNTASTIC_VERSION = '3.8.0-64'
 lockvar g:_SYNTASTIC_VERSION
 
 " Sanity checks {{{1