review feedback

Author: tonbut

modules/ROOT/pages/procedures.adoc

@@ -74,6 +74,16 @@ For more information, see xref:authentication-authorization/index.adoc[Authentic
 | *Mode* 3+| DBMS
 |===
 
+[procedure_dbms_security_reload_tls]]
+=== dbms.security.reloadTLS()
+
+
+.Details
+|===
+| *Syntax* 3+m| dbms.security.reloadTLS()
+| *Description* 3+a| Trigger the dynamic reloading of all TLS certificates and configuration.
+| *Mode* 3+| DBMS
+|===
 
 [[procedure_dbms_showcurrentuser]]
 === dbms.showCurrentUser()

modules/ROOT/pages/security/ssl-framework.adoc

@@ -1125,7 +1125,7 @@ It is best to do this when the cluster is deployed as changing this configuratio
 
 [source, properties]
 ----
-dbms.security.tls_reload=true (default is false)
+dbms.security.tls_reload_enabled=true (default is false)
 ----
 
 . Replace old certificates either by overwriting on the filesystem or by copying them to a new location and updating the required SSL configuration for each effected scope.
@@ -1138,7 +1138,7 @@ New certificates need to be copied to all cluster members as required.
 
 [source]
 ----
-dbms.reloadTLSCertificates()
+dbms.security.reloadTLS()
 ----
 
 . New settings will take effect immediately, however existing connections will not be pre-emptively terminated.