Merge pull request GeoNode#2 from Geocent/master

Changes from integration branch to keep master up to date

README

@@ -2,9 +2,17 @@
     :alt: Build Status
     :target: http://travis-ci.org/GeoNode/geonode
 
-=========
- GeoNode
-=========
+
+GeoNode Support
+===============
+
+To get support, give feedbacks and suggestions please use the GeoNode official channels, the users mailing list: http://lists.osgeo.org/pipermail/geonode-users/ and the developers mailing list: http://lists.osgeo.org/pipermail/geonode-devel/.
+
+This repository is used to track code changes and GeoNode issues, please DON'T open new issues to ask for support.
+
+
+GeoNode Installation
+====================
 
 If you just want to try GeoNode, it is recommended to use Ubuntu 12.04 and install the python software properties.::
 
@@ -190,7 +198,7 @@ Geonode's development roadmap is documented in a series of Geonode Improvement P
 They are documented here: https://github.com/GeoNode/geonode/wiki/GeoNode-Improvement-Proposals.
 GNIPS are considered to be large undertakings which will add a large amount of features to the project. 
 As such they are the topic of community dicussion and guidance.
-The community discusses these on the developer mailing list: https://groups.google.com/a/opengeo.org/forum/#!forum/geonode-dev
+The community discusses these on the developer mailing list: http://lists.osgeo.org/pipermail/geonode-devel/
 Github issues tracks features and bugs, for new developers the tag 'easy-pick' indicates an 
 issue that should be relatively easy for new developers to understand and complete. Once you have completed an issue
 a pull request should be submitted. This will then be reviewed by the community.

docs/organizational/community_resources.txt

@@ -19,10 +19,10 @@ Community Contact
 Contact members and ask questions
 
 * Mailing Lists
-    * Users Forum https://groups.google.com/forum/#!forum/geonode-users
-    * Developers Forum https://groups.google.com/a/opengeo.org/group/geonode-dev/topics
-* Announcements https://groups.google.com/a/opengeo.org/forum/#!forum/geonode-announcements
-* IRC irc://irc.freenode.net/geonode (logs?)
+    * Users List http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
+    * Developers List http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel
+* IRC irc://irc.freenode.net/geonode
+* WebChat: http://webchat.freenode.net/?channels=#geonode
 * Social Media
     * Blog http://geonode.org/blog/
     * Twitter https://twitter.com/geonode
@@ -111,4 +111,4 @@ Public Sites
 
 * Risiko (Risk in a Box) demo site http://demo.riskinabox.org/
 * CIGNo network: CNR - ISMAR Node http://cigno.ve.ismar.cnr.it/
-* ... Many Many More
+* ... Many Many More

docs/tutorials/admin/admin_panel/base.txt

@@ -30,7 +30,7 @@ Restriction Code Types
 
 Being GeoNode strictly tied to the standards, the restrictions cannot be added/deleted or modified in their identifier. This behavior is necessary to keep the consistency in case of federation with the CSW catalogues.
 
-The Restrictions GeoNode description field can in any case be modified is some kind of customisation is necessary, since it's just the string that will appear on the layer metadata page. If some of the restrictions are not needed within the GeoNode instance, it is possible to hide them by unchecking the "Is choice" field.
+The Restrictions GeoNode description field can in any case be modified if some kind of customisation is necessary, since it's just the string that will appear on the layer metadata page. If some of the restrictions are not needed within the GeoNode instance, it is possible to hide them by unchecking the "Is choice" field.
 
 .. figure:: img/admin-base-restriction-list.png