diff --git a/multi/multi__spring_cloud_context_application_context_services.html b/multi/multi__spring_cloud_context_application_context_services.html
index fd5ac116..6821441a 100644
--- a/multi/multi__spring_cloud_context_application_context_services.html
+++ b/multi/multi__spring_cloud_context_application_context_services.html
@@ -81,4 +81,5 @@ In that case, it is rebuilt on a refresh and its dependencies are re-injected. A
It follows the same rules as the Config Server and has the same external configuration through encrypt.*.
Thus, you can use encrypted values in the form of {cipher}* and, as long as there is a valid key, they are decrypted before the main application context gets the Environment settings.
To use the encryption features in an application, you need to include Spring Security RSA in your classpath (Maven co-ordinates: "org.springframework.security:spring-security-rsa"), and you also need the full strength JCE extensions in your JVM.
If you get an exception due to "Illegal key size" and you use Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. -See the following links for more information:
Extract the files into the JDK/jre/lib/security folder for whichever version of JRE/JDK x64/x86 you use.
For a Spring Boot Actuator application, some additional management endpoints are available. You can use:
POST to /actuator/env to update the Environment and rebind @ConfigurationProperties and log levels./actuator/refresh to re-load the boot strap context and refresh the @RefreshScope beans./actuator/restart to close the ApplicationContext and restart it (disabled by default)./actuator/pause and /actuator/resume for calling the Lifecycle methods (stop() and start() on the ApplicationContext).