test

doc/guides/1 - Getting Started/3 - Generate an Extension to Use Your MVCs.md

@@ -31,7 +31,7 @@ Since an extension is a kind of engine, it has the same familiar directory struc
 Refinery ships with an extension generator that makes adding your own functionality a breeze. It works just like the Rails scaffold generator: given information about a model, it will automatically generate the necessary model, view, controller, configuration, and database files for you and will put them into their appropriate directories. Here's the command:
 
 ```shell
-$ rails generate refinery:engine singular_model_name attribute:type [attribute:type …]
+$ rails generate refinery:engine singular_model_name attribute:type [attribute:type ...]
 ```
 __TIP__: to see all the options supported by the `refinery:engine` generator just run `rails g refinery:engine`.
 
@@ -93,7 +93,7 @@ This results in the following:
  create vendor/extensions/events/lib/tasks/events.rake
  create vendor/extensions/events/readme.md
  create vendor/extensions/events/refinerycms-events.gemspec
- …
+ ...
 ------------------------
 Now run:
 bundle install
@@ -113,7 +113,7 @@ $ rake db:migrate
 $ rake db:seed
 ```
 
-A line for the events extension has been added in the Gemfile of your application. `bundle install` will verify and load the extension. A generator has been created for you that will automatically create the event table and db seed calls for you: `rails generate refinery:events` will generate the migration and db seed files for the extension based on the fields you specified in the `rails generate refinery:engine …` command. And finally, running `rake db:migrate` and `rake db:seed` will load and run the migration and db:seed files that you just generated for the events extension. .
+A line for the events extension has been added in the Gemfile of your application. `bundle install` will verify and load the extension. A generator has been created for you that will automatically create the event table and db seed calls for you: `rails generate refinery:events` will generate the migration and db seed files for the extension based on the fields you specified in the `rails generate refinery:engine ...` command. And finally, running `rake db:migrate` and `rake db:seed` will load and run the migration and db:seed files that you just generated for the events extension. .
 
 When you run bundle install, you may see a message that says
 
@@ -122,7 +122,7 @@ When you run bundle install, you may see a message that says
    authors may not be empty
 ```
 
-This is a warning message from RubyGems telling you that no author is specified for this extension. This is only important if you are going to create a gem from this extension. You can safely ignore this message. If you do want to resolve it and get rid of the message, you can edit the [gem specification file](http://guides.rubygems.org/specification-reference/) for the extension `refinerycms-events.gemspec` and put your name in there as the author. Just put this line: `s.author = 'yourname'` in the do block (after the `s.version….` line is fine).
+This is a warning message from RubyGems telling you that no author is specified for this extension. This is only important if you are going to create a gem from this extension. You can safely ignore this message. If you do want to resolve it and get rid of the message, you can edit the [gem specification file](http://guides.rubygems.org/specification-reference/) for the extension `refinerycms-events.gemspec` and put your name in there as the author. Just put this line: `s.author = 'yourname'` in the do block (after the `s.version....` line is fine).
 
 __TIP__: When new extensions are added it's a good idea to restart your server for new changes to be loaded in.