diff --git a/docs/user/production-considerations/production.asciidoc b/docs/user/production-considerations/production.asciidoc
index 6396e0c98300c..84727e536cfe9 100644
--- a/docs/user/production-considerations/production.asciidoc
+++ b/docs/user/production-considerations/production.asciidoc
@@ -27,16 +27,11 @@ you can configure {kib} to use a list of {es} hosts.
 To serve multiple {kib} installations behind a load balancer, you must change the configuration.
 See {kibana-ref}/settings.html[Configuring {kib}] for details on each setting.
 
-Settings unique across each {kib} instance:
+These settings must be unique across each {kib} instance:
 [source,js]
 --------
-server.uuid
+server.uuid // if not provided, this is autogenerated
 server.name
---------
-
-Settings unique across each host (for example, running multiple installations on the same virtual machine):
-[source,js]
---------
 path.data
 pid.file
 server.port
@@ -106,7 +101,7 @@ These can be used to automatically update the list of hosts as a cluster is resi
 [[memory]]
 === Memory
 
-Kibana has a default memory limit that scales based on total memory available.  In some scenarios, such as large reporting jobs, 
+Kibana has a default memory limit that scales based on total memory available.  In some scenarios, such as large reporting jobs,
 it may make sense to tweak limits to meet more specific requirements.
 
 A limit can be defined by setting `--max-old-space-size` in the `node.options` config file found inside the `kibana/config` folder or any other folder configured with the environment variable `KBN_PATH_CONF`. For example, in the Debian-based system, the folder is `/etc/kibana`.