Update community.html

app/views/community.html

@@ -183,7 +183,7 @@ <h3>Requirement Definition</h3>
                     project lead will then publish the roadmap on the developers mailing list, and update the version information in
                     JIRA. All requirements are fed into the same community process that our community users follow. We create JIRAs for
                     all feature requests on our schedule. The best way for you to suggest requirements for a future release of Forge is
-                    to enter a feature request in JIRA. Lobbying for features using the voting feature in JIRA, and posting to the
+                    to enter a feature request in  <a href="https://issues.jboss.org/browse/FORGE" target="_new">JIRA</a>. Lobbying for features using the voting feature in JIRA, and posting to the
                     community forums, is a great way to express interest as well. Although, contributing is the single most expedient
                     way to get a capability into a particular release.</p>
             </div>
@@ -199,9 +199,8 @@ <h3>Release Cycle</h3>
             <div class="col-sm-12">
                 <h3>Contribution</h3>
                 <p>
-                    Forge welcomes, thrives on and greatly values community contribution. Please see our
-                    <h:link outcome="/community">Community</h:link>
-                    page for more information on how to contribute to Forge.
+                    Forge welcomes, thrives on and greatly values community contribution. 
+                    You should find how to contribute to Forge in this Community page.
                 </p>
             </div>
         </div>