Update docu about contributing patches/PRs
Fix few minor typos in README.txt
diff --git a/README.txt b/README.txt
index 2374a79..4563583 100644
--- a/README.txt
+++ b/README.txt
@@ -1,4 +1,4 @@
-Note: the branch trnk is obsolete. Please use the master branch.
+Note: the branch trunk is obsolete. Please use the master branch.
----
The Apache Velocity Project
@@ -62,7 +62,7 @@
-------------------------------
To build the site, enter the "site" directory and run "mvn" (the
- default goal here is "site-post" which generates the site and also
+ default goal here is "post-site" which generates the site and also
installs a few extra files (e.g. the download.cgi script for
automatic mirror selection).
diff --git a/src/content/get-involved.mdtext b/src/content/get-involved.mdtext
index 51a1fd3..360b816 100644
--- a/src/content/get-involved.mdtext
+++ b/src/content/get-involved.mdtext
@@ -19,9 +19,9 @@
In this role, you participate in the actual development of the code. If this is the type of role you'd like to play, here are some steps (in addition to the ones above) to get you started:
+ [Read Guidelines](/how-it-works.html)
-+ Check Online Oocumentation
++ [Check Online Documentation](/engine/devel/getting-started.html)
+ [Download the Source Code](/download.cgi)
-+ Contribute Patches
++ Contribute Patches - the easiest way is to create a Pull Request (PR) at GitHub: [Engine](https://github.com/apache/velocity-engine/pulls) and [Tools](https://github.com/apache/velocity-tools/pulls). All PRs are automatically tested at TravisCI on both AMD64 and ARM64 CPU architectures.
Here is one developer's advice how to get involved. It specifically talks about Tomcat, but the general idea can applied to any of the projects.
