apex-site git commit: Fix links.

[th...@apache.org]

Repository: apex-site
Updated Branches:
  refs/heads/master ef6dfa014 -> c3a284ba0


Fix links.


Project: http://git-wip-us.apache.org/repos/asf/apex-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/apex-site/commit/c3a284ba
Tree: http://git-wip-us.apache.org/repos/asf/apex-site/tree/c3a284ba
Diff: http://git-wip-us.apache.org/repos/asf/apex-site/diff/c3a284ba

Branch: refs/heads/master
Commit: c3a284ba04d860705af016afe3348f0e523f48c1
Parents: ef6dfa0
Author: Thomas Weise <th...@datatorrent.com>
Authored: Tue Sep 6 18:50:47 2016 -0700
Committer: Thomas Weise <th...@datatorrent.com>
Committed: Tue Sep 6 18:50:47 2016 -0700

----------------------------------------------------------------------
 src/md/community.md           | 2 +-
 src/md/malhar-contributing.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/apex-site/blob/c3a284ba/src/md/community.md
----------------------------------------------------------------------
diff --git a/src/md/community.md b/src/md/community.md
index 92beeea..eea6767 100644
--- a/src/md/community.md
+++ b/src/md/community.md
@@ -25,7 +25,7 @@ List of organizations using Apache Apex is available at [Powered by Apex](/power
 
 # Contributing
 
-Looking for ideas to get involved? Please see [JIRA tickets for newcomers](https://issues.apache.org/jira/issues/?jql=project%20in%20%28APEXCORE%2C%20APEXMALHAR%29%20and%20labels%20%3D%20newbie) and pick a ticket. Please also sign up to the dev mailing list and JIRA. 
+Looking for ideas to get involved? Please see [JIRA tickets for newcomers](https://issues.apache.org/jira/issues/?jql=project%20in%20%28APEXCORE%2C%20APEXMALHAR%29%20and%20resolution%20%3D%20Unresolved%20and%20labels%20%3D%20newbie) and pick a ticket. Please also sign up to the dev mailing list and JIRA. 
 
 **To learn more about contributing to the project, [check out the contributing guidelines](/contributing.html).**
 

http://git-wip-us.apache.org/repos/asf/apex-site/blob/c3a284ba/src/md/malhar-contributing.md
----------------------------------------------------------------------
diff --git a/src/md/malhar-contributing.md b/src/md/malhar-contributing.md
index 218f167..3994d7f 100644
--- a/src/md/malhar-contributing.md
+++ b/src/md/malhar-contributing.md
@@ -25,11 +25,11 @@ If after performing the above analysis, there is a need to write a new operator
 
 ## Implementing an operator
 
-* Look at the [Operator Development Guide](/docs/apex/operator_development) and the [Best Practices Guide](/docs/malhar/development_best_practices) on how to implement an operator and what the dos and don'ts are.
+* Look at the [Operator Development Guide](/docs/apex/operator_development) and the [Best Practices Guide](/docs/apex/development_best_practices) on how to implement an operator and what the dos and don'ts are.
 * Refer to existing operator implementations when in doubt or unsure about how to implement some functionality. You can also email the [dev mailing list](/community.html#mailing-lists) with any questions.
 * Write unit tests for operators
 	* Refer to unit tests for existing operators.
 	* If possible write a sample application testing the operator.
 	* Try to keep the tests self contained i.e., avoid the user having to perform additional setup or setup other services before running the tests. This can be done by starting mock versions of the required services from within the test and shutting them down when the test finishes.
 * Follow the code style guidelines of the Apache Apex project described [here](http://apex.apache.org/contributing.html#code-style).
-* If only the core operator business logic for the operator is implemented and advanced platform functionality for scalability and recovery, such as partitioning, idempotence etc., described in the above reference guides are not implemented, make the code submission pull request to the **contrib** folder in Malhar, otherwise make it to an appropriate top-level module or a new one if one is not present.
\ No newline at end of file
+* If only the core operator business logic for the operator is implemented and advanced platform functionality for scalability and recovery, such as partitioning, idempotence etc., described in the above reference guides are not implemented, make the code submission pull request to the **contrib** folder in Malhar, otherwise make it to an appropriate top-level module or a new one if one is not present.