<NME> README.md
<BEF> The `rspec` command comes with several options you can use to customize RSpec's
behavior, including output formats, filtering examples, etc.

For a full list of options, run the `rspec` command with the `--help` flag:

    $ rspec --help

<MSG> update docs

<DFF> @@ -4,3 +4,25 @@ behavior, including output formats, filtering examples, etc.
 For a full list of options, run the `rspec` command with the `--help` flag:
 
     $ rspec --help
+
+### Run with `ruby`
+
+Generally, life is simpler if you just use the `rspec` command. If you must use the `ruby`
+command, however, you'll want to do the following:
+
+* `require 'rspec/autorun'`
+
+This tells RSpec to run your examples.  Do this in any file that you are
+passing to the `ruby` command.
+
+* Update the `LOAD_PATH`
+
+It is conventional to put configuration in and require assorted support files
+from `spec/spec_helper.rb`. It is also conventional to require that file from
+the spec files using `require 'spec_helper'`. This works because RSpec
+implicitly adds the `spec` directory to the `LOAD_PATH`. It also adds `lib`, so
+your implementation files will be on the `LOAD_PATH` as well.
+
+If you're using the `ruby` command, you'll need to do this yourself:
+
+    ruby -Ilib -Ispec path/to/spec.rb

{'commit': "diff --git a/features/.nav b/features/.nav\nindex dec7aac8..25b607b4 100644\n--- a/features/.nav\n+++ b/features/.nav\n@@ -5,6 +5,15 @@\n   - basic_structure.feature\n   - shared_example_group.feature\n   - shared_context.feature\n+- command_line:\n+  - configure.feature\n+  - example_name_option.feature\n+  - format_option.feature\n+  - line_number_option.feature\n+  - tag.feature\n+  - line_number_appended_to_path.feature\n+  - exit_status.feature\n+  - rake_task.feature\n - pending:\n   - pending_examples.feature\n - hooks:\n@@ -29,15 +38,6 @@\n   - exclusion_filters.feature\n   - if_and_unless.feature\n   - run_all_when_everything_filtered.feature\n-- command_line:\n-  - configure.feature\n-  - example_name_option.feature\n-  - format_option.feature\n-  - line_number_option.feature\n-  - tag.feature\n-  - line_number_appended_to_path.feature\n-  - exit_status.feature\n-  - rake_task.feature\n - configuration:\n   - read_options_from_file.feature\n   - fail_fast.feature\ndiff --git a/features/command_line/README.md b/features/command_line/README.md\nindex d7955c3f..e86c4312 100644\n--- a/features/command_line/README.md\n+++ b/features/command_line/README.md\n@@ -4,3 +4,25 @@ behavior, including output formats, filtering examples, etc.\n For a full list of options, run the `rspec` command with the `--help` flag:\n \n     $ rspec --help\n+\n+### Run with `ruby`\n+\n+Generally, life is simpler if you just use the `rspec` command. If you must use the `ruby`\n+command, however, you'll want to do the following:\n+\n+* `require 'rspec/autorun'`\n+\n+This tells RSpec to run your examples.  Do this in any file that you are\n+passing to the `ruby` command.\n+\n+* Update the `LOAD_PATH`\n+\n+It is conventional to put configuration in and require assorted support files\n+from `spec/spec_helper.rb`. It is also conventional to require that file from\n+the spec files using `require 'spec_helper'`. This works because RSpec\n+implicitly adds the `spec` directory to the `LOAD_PATH`. It also adds `lib`, so\n+your implementation files will be on the `LOAD_PATH` as well.\n+\n+If you're using the `ruby` command, you'll need to do this yourself:\n+\n+    ruby -Ilib -Ispec path/to/spec.rb\n", 'commit_subject': 'update docs', 'repo_name': 'rspec/rspec-core', 'committer': {'name': 'David Chelimsky', 'email': 'f7cb1b4a2064ae0fe0ec6b9386cc618064212b58@gmail.com', 'time_sec': '1304871741', 'tz_offset': '-300', 'date': {'seconds': '1304871741'}}, 'commit_tree': '28e56d73f57df7cf3dc56dc7a46c09e847fb4faf', 'commit_message': 'update docs\n', 'language_name': 'HTML', 'license': 'mit', 'hunks': "@@ -4,3 +4,25 @@ behavior, including output formats, filtering examples, etc.\n For a full list of options, run the `rspec` command with the `--help` flag:\n \n     $ rspec --help\n+\n+### Run with `ruby`\n+\n+Generally, life is simpler if you just use the `rspec` command. If you must use the `ruby`\n+command, however, you'll want to do the following:\n+\n+* `require 'rspec/autorun'`\n+\n+This tells RSpec to run your examples.  Do this in any file that you are\n+passing to the `ruby` command.\n+\n+* Update the `LOAD_PATH`\n+\n+It is conventional to put configuration in and require assorted support files\n+from `spec/spec_helper.rb`. It is also conventional to require that file from\n+the spec files using `require 'spec_helper'`. This works because RSpec\n+implicitly adds the `spec` directory to the `LOAD_PATH`. It also adds `lib`, so\n+your implementation files will be on the `LOAD_PATH` as well.\n+\n+If you're using the `ruby` command, you'll need to do this yourself:\n+\n+    ruby -Ilib -Ispec path/to/spec.rb\n", 'addition_count': 22, 'deletion_count': 0, 'src_file': 'a/features/command_line/README.md', 'tgt_file': 'b/features/command_line/README.md', 'file_extension': '.md', 'before_file': "The `rspec` command comes with several options you can use to customize RSpec's\nbehavior, including output formats, filtering examples, etc.\n\nFor a full list of options, run the `rspec` command with the `--help` flag:\n\n    $ rspec --help\n", 'message': 'update docs\n', 'author_name': 'David Chelimsky', 'lang': 'md'}