libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions

fixed typos

Browse source
This commit is contained in:
Chuck Copello 2016-12-06 15:53:48 -05:00
parent ec4b42b65a
commit 7a5ae64de3
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
topics/cache/replication.adoc vendored
View file

@ -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 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. out when a node goes down, then one owner is good enough and you will avoid replication.

2
topics/database/datasource.adoc
View file

@ -4,7 +4,7 @@
After declaring your JDBC driver, you have to modify the existing datasource configuration that {{book.project.name}} uses 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 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 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 .Declare Your JDBC Drivers
[source,xml] [source,xml]