Incorporate wording change suggested by Magnus

diff --git a/template/pages/user_group_recognition.html b/template/pages/user_group_recognition.html
index 1dd1c8838da90d4d2587bf10b5daaef7aea9d292..7506829655f1fe03a65ef4f25b858e0009e9a8e3 100644 (file)
--- a/template/pages/user_group_recognition.html
+++ b/template/pages/user_group_recognition.html
@@ -12,7 +12,7 @@ Use of the terms “must”, “must not”, “should” and “should not” i
 <ul>
   <li>The Community User Group must be primarily focused on PostgreSQL, and related technologies. User Groups that target a broad range of database products are not considered Community User Groups in this context.</li>
   <li>The PostgreSQL Europe Board reserves the right to recognise, not recognise, or rescind a previous recognition for any Community User Group without justification.</li>
-  <li>Community User Groups are for the entire PostgreSQL community and are public in nature. Anyone may attend and there must not be any requirement for a Non-Disclosure Agreement (NDA) or similar contract for an attendee to attend the event.</li>
+  <li>Community User Groups are for the entire PostgreSQL community and are public in nature. Anyone may attend and there must not be any requirement for a Non-Disclosure Agreement (NDA) or similar contract for an attendee to attend.</li>
   <li>The Community User Group must adopt and follow an appropriate Code of Conduct to ensure a safe and enjoyable environment for anyone who wishes to attend. PostgreSQL Europe suggests, but does not require, that one based on the PGConf.EU Code of Conduct is used if there are no special reasons to use a different one.</li>
   <li>The Community User Group must have at least one event every three months in a calendar year in order to maintain its recognition as a Community User Group.</li>
   <li>These criteria may be reviewed and potentially updated at any time.</li>