Merge pull request #203 from pnicolucci/UpdateServerPagesFootnote

Issue #114: Update Server Pages reference in footnote

spec/src/main/asciidoc/jakarta-stl.adoc

@@ -416,7 +416,7 @@ visible within the body of the action and are stored in "page"
 scopefootnote:[Since nested scoped variables are always saved in page scope, no scope attribute is associated with them.]. The action must create the variable
 according to the semantics of _PageContext.setAttribute(varName,PAGE_SCOPE)_, and it must remove it at the end of the action according
 to the semantics of _PageContext.removeAttribute(varName, PAGE_SCOPE)_
-.footnote:[It is important to note that the Jakarta Server Pages specification says that "A name should refer to a unique object at all points in the execution, that is all the different scopes really should behave as a single name space." The Jakarta Server Pages specification also says that "A Jakarta Server Pages container implementation may or may not enforce this rule explicitly due to performance reasons". Because of this, if a scoped variable with the same name as a nested variable already exists in a scope other than 'page', exactly what happens to that scoped variable depends on how the Jakarta Server Pages container has been implemented. To comply with the Jakarta Server Pages specification, and to avoid non-portable behavior, page authors should therefore avoid using the same name in different scopes.]
+.footnote:[It is important to note that the Jakarta Server Pages specification section 1.8.2 says that "A name should refer to a unique object at all points in the execution; that is, all the different scopes really should behave as a single name space." The Jakarta Server Pages specification also says that "A JSP container implementation may or may not enforce this rule explicitly for performance reasons.". Because of this, if a scoped variable with the same name as a nested variable already exists in a scope other than 'page', exactly what happens to that scoped variable depends on how the Jakarta Server Pages container has been implemented. To comply with the Jakarta Server Pages specification, and to avoid non-portable behavior, page authors should therefore avoid using the same name in different scopes.]
 
 At-end scoped variables are only visible at
 the end of the action. Their lifecycle is the one associated with their