aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRyuta Kamizono <kamipo@gmail.com>2017-08-22 14:57:01 +0900
committerGitHub <noreply@github.com>2017-08-22 14:57:01 +0900
commit1fe41329c6ffcbb52c9762d28d780e838584e63d (patch)
treec307908951b479ed132495810087ca825af4f131
parent1cc45ade33f437762af07575bfdc0d2acabed0d8 (diff)
parente9f71e2451c5be81941ede6c134290999969513e (diff)
downloadrails-1fe41329c6ffcbb52c9762d28d780e838584e63d.tar.gz
rails-1fe41329c6ffcbb52c9762d28d780e838584e63d.tar.bz2
rails-1fe41329c6ffcbb52c9762d28d780e838584e63d.zip
Merge pull request #30357 from ydakuka/missing-backquotes
missing backquotes [ci skip]
-rw-r--r--guides/source/action_mailer_basics.md2
-rw-r--r--guides/source/getting_started.md2
-rw-r--r--guides/source/plugins.md4
3 files changed, 4 insertions, 4 deletions
diff --git a/guides/source/action_mailer_basics.md b/guides/source/action_mailer_basics.md
index 6562dc3a98..ba26c922be 100644
--- a/guides/source/action_mailer_basics.md
+++ b/guides/source/action_mailer_basics.md
@@ -560,7 +560,7 @@ Unlike controllers, the mailer instance doesn't have any context about the
incoming request so you'll need to provide the `:asset_host` parameter yourself.
As the `:asset_host` usually is consistent across the application you can
-configure it globally in config/application.rb:
+configure it globally in `config/application.rb`:
```ruby
config.action_mailer.asset_host = 'http://example.com'
diff --git a/guides/source/getting_started.md b/guides/source/getting_started.md
index 385b99ea6b..11c7ef9125 100644
--- a/guides/source/getting_started.md
+++ b/guides/source/getting_started.md
@@ -178,7 +178,7 @@ of the files and folders that Rails created by default:
|lib/|Extended modules for your application.|
|log/|Application log files.|
|public/|The only folder seen by the world as-is. Contains static files and compiled assets.|
-|Rakefile|This file locates and loads tasks that can be run from the command line. The task definitions are defined throughout the components of Rails. Rather than changing Rakefile, you should add your own tasks by adding files to the lib/tasks directory of your application.|
+|Rakefile|This file locates and loads tasks that can be run from the command line. The task definitions are defined throughout the components of Rails. Rather than changing Rakefile, you should add your own tasks by adding files to the `lib/tasks` directory of your application.|
|README.md|This is a brief instruction manual for your application. You should edit this file to tell others what your application does, how to set it up, and so on.|
|test/|Unit tests, fixtures, and other test apparatus. These are covered in [Testing Rails Applications](testing.html).|
|tmp/|Temporary files (like cache and pid files).|
diff --git a/guides/source/plugins.md b/guides/source/plugins.md
index 164207a9f9..0f0cde7634 100644
--- a/guides/source/plugins.md
+++ b/guides/source/plugins.md
@@ -135,7 +135,7 @@ To test that your method does what it says it does, run the unit tests with `bin
2 runs, 2 assertions, 0 failures, 0 errors, 0 skips
```
-To see this in action, change to the test/dummy directory, fire up a console and start squawking:
+To see this in action, change to the `test/dummy` directory, fire up a console and start squawking:
```bash
$ bin/rails console
@@ -439,7 +439,7 @@ send("#{self.class.yaffle_text_field}=", string.to_squawk)
Generators
----------
-Generators can be included in your gem simply by creating them in a lib/generators directory of your plugin. More information about
+Generators can be included in your gem simply by creating them in a `lib/generators` directory of your plugin. More information about
the creation of generators can be found in the [Generators Guide](generators.html).
Publishing Your Gem