diff --git a/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp b/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp
index 04d01e98b4..02758ef0b8 100644
--- a/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp
+++ b/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp
@@ -4,7 +4,7 @@
Contacts Security Demo
Contacts Security Demo
-Contacts demonstrates the following central Acegi Security capabilities:
+
Contacts demonstrates the following central Spring Security capabilities:
- Role-based security. Each principal is a member of certain roles,
which are used to restrict access to certain secure objects.
@@ -15,20 +15,20 @@
layer bean has a number of secured (protected) and public (unprotected)
methods.
- Web request security. The
/secure URI path is protected
- by Acegi Security from principals not holding the
+ by Spring Security from principals not holding the
ROLE_USER granted authority.
- Security unaware application objects. None of the objects
- are aware of the security being implemented by Acegi Security. *
-- Security taglib usage. All of the JSPs use Acegi Security's
+ are aware of the security being implemented by Spring Security. *
+- Security taglib usage. All of the JSPs use Spring Security's
taglib to evaluate security information. *
- Fully declarative security. Every capability is configured in
- the application context using standard Acegi Security classes. *
+ the application context using standard Spring Security classes. *
- Database-sourced security data. All of the user, role and ACL
information is obtained from an in-memory JDBC-compliant database.
- Integrated form-based and BASIC authentication. Any BASIC
authentication header is detected and used for authentication. Normal
interactive form-based authentication is used by default.
-- Remember-me services. Acegi Security's pluggable remember-me
+
- Remember-me services. Spring Security's pluggable remember-me
strategy is demonstrated, with a corresponding checkbox on the login form.