fixed typos
This commit is contained in:
parent
ec4b42b65a
commit
7a5ae64de3
2 changed files with 2 additions and 2 deletions
2
topics/cache/replication.adoc
vendored
2
topics/cache/replication.adoc
vendored
|
@ -18,7 +18,7 @@ You can change the number of nodes that replicate a piece of data by change the
|
|||
...
|
||||
----
|
||||
|
||||
Here's we've changed it so at least two nodes will replicate one specific user login session.
|
||||
Here we've changed it so at least two nodes will replicate one specific user login session.
|
||||
|
||||
TIP: The number of owners recommended is really dependent on your deployment. If you do not care if users are logged
|
||||
out when a node goes down, then one owner is good enough and you will avoid replication.
|
||||
|
|
|
@ -4,7 +4,7 @@
|
|||
After declaring your JDBC driver, you have to modify the existing datasource configuration that {{book.project.name}} uses
|
||||
to connect it to your new external database. You'll do
|
||||
this within the same configuration file and XML block that you registered your JDBC driver in. Here's an example
|
||||
that set's up the connection to your new database:
|
||||
that sets up the connection to your new database:
|
||||
|
||||
.Declare Your JDBC Drivers
|
||||
[source,xml]
|
||||
|
|
Loading…
Reference in a new issue