aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source
diff options
context:
space:
mode:
authorAbhay Nikam <nikam.abhay1@gmail.com>2019-06-04 20:42:52 +0530
committerAbhay Nikam <nikam.abhay1@gmail.com>2019-06-04 20:57:32 +0530
commitc7a609b10caf0185cb9f8d80908e111992b48f7d (patch)
tree87045e444c89577a9552327094b5041ee29fe74f /guides/source
parentf614be3768c41fe080457d90c696d1df047d3357 (diff)
downloadrails-c7a609b10caf0185cb9f8d80908e111992b48f7d.tar.gz
rails-c7a609b10caf0185cb9f8d80908e111992b48f7d.tar.bz2
rails-c7a609b10caf0185cb9f8d80908e111992b48f7d.zip
Fix typo in multi database guide depentent -> dependent [ci skip]
Fixed the redundant addition of to [ci skip]
Diffstat (limited to 'guides/source')
-rw-r--r--guides/source/active_record_multiple_databases.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/active_record_multiple_databases.md b/guides/source/active_record_multiple_databases.md
index 3e445b57a1..e2c7878118 100644
--- a/guides/source/active_record_multiple_databases.md
+++ b/guides/source/active_record_multiple_databases.md
@@ -81,7 +81,7 @@ When using multiple databases there are a few important settings.
First, the database name for the primary and replica should be the same because they contain
the same data. Second, the username for the primary and replica should be different, and the
-replica user's permissions should be to to read and not write.
+replica user's permissions should be to read and not write.
When using a replica database you need to add a `replica: true` entry to the replica in the
`database.yml`. This is because Rails otherwise has no way of knowing which one is a replica
@@ -260,7 +260,7 @@ if you need sharding it may be advisable to continue using one of the many gems
that supports this.
Rails also doesn't support automatic load balancing of replicas. This is very
-depentent on your infrastructure. We may implement basic, primitive load balancing
+dependent on your infrastructure. We may implement basic, primitive load balancing
in the future, but for an application at scale this should be something your application
handles outside of Rails.