[struts-site] 01/02: Fixes example with list variable

[lu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

lukaszlenart pushed a commit to branch small-fixes
in repository https://gitbox.apache.org/repos/asf/struts-site.git

commit 35db3b56f18068274d8dabb8c5fd9a53629900d1
Author: Lukasz Lenart <lu...@apache.org>
AuthorDate: Fri Oct 18 15:25:50 2019 +0200

    Fixes example with list variable
---
 source/tag-developers/freemarker-tags.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/tag-developers/freemarker-tags.md b/source/tag-developers/freemarker-tags.md
index 5c40f4c..421a850 100644
--- a/source/tag-developers/freemarker-tags.md
+++ b/source/tag-developers/freemarker-tags.md
@@ -93,12 +93,12 @@ In the new template, the description is referenced via the parameters Map: `${pa
 
 ## Attribute Types
 
-Remember that all tag attributes must first be set as Strings - they are then later evaluated (using [OGNL](ognl.html)) 
+Remember that all tag attributes must first be set as Strings - they are then later evaluated (using [OGNL](ognl)) 
 to a different type, such as List, int, or boolean. This generally works just fine, but it can be limiting when using 
 FreeMarker which provides more advanced ways to apply attributes. Suppose the following example:
 
 ```ftl
-<@s.select label="Foo label - %{foo}" name="%{name}" list="%{{1, 2, 3}}"/>
+<@s.select label="Foo label - %{foo}" name="%{name}" list="%{1, 2, 3}"/>
 ```
 
 What will happen here is that each attribute will be evaluated to a String as best it can. This may involve calling the