JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rabbitmq module: Update documentation after proofreading

Browse Source 
Thanks @c0bw3b, @lsix!
This commit is contained in:
Robert Hensing 2018-11-03 19:17:45 +01:00
parent 6c568b6644
commit 4aa30166d1
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
nixos/modules/services/amqp/rabbitmq.nix
View File

@ -95,7 +95,7 @@ in {
If you do need to express nested data structures, you can use If you do need to express nested data structures, you can use
<literal>config</literal> option. Configuration from <literal>config</literal> <literal>config</literal> option. Configuration from <literal>config</literal>
will be merged into the these options by RabbitMQ at runtime to will be merged into these options by RabbitMQ at runtime to
form the final configuration. form the final configuration.
See http://www.rabbitmq.com/configure.html#config-items See http://www.rabbitmq.com/configure.html#config-items
@ -110,7 +110,7 @@ in {
Verbatim advanced configuration file contents using the Erlang syntax. Verbatim advanced configuration file contents using the Erlang syntax.
This is also known as the <literal>advanced.config</literal> file or the old config format. This is also known as the <literal>advanced.config</literal> file or the old config format.
Where possible, the use <literal>configItems</literal> is preferred. However, nested <literal>configItems</literal> is preferred whenever possible. However, nested
data structures can only be expressed properly using the <literal>config</literal> option. data structures can only be expressed properly using the <literal>config</literal> option.
The contents of this option will be merged into the <literal>configItems</literal> The contents of this option will be merged into the <literal>configItems</literal>