updating according to review

Author: mhmohona

newsfeed/demo/announcements.rst

@@ -32,7 +32,7 @@ Announcements
     to anaconda.org. Direct uploads to the ``conda-forge`` channel will no
     longer work. If you are having trouble with package uploads, please
     rerender your feedstock with the latest version of ``conda-smithy``.
-    As always, if you need help, bump us on element chatroom or GitHub!
+    As always, if you need help, bump us on gitter or GitHub!
 
 :2020-08-06: Fixed Maintenance Process for Feedstock Teams
 
@@ -173,7 +173,7 @@ Announcements
 
     Despite our extensive testing, we do not expect this change to be completely smooth,
     so please bear with us. As always, if you have any questions, concerns, or trouble, you
-    can find us on Element chatroom or bump us directly on github!
+    can find us on gitter or bump us directly on github!
 
 :2020-03-24: ``vs2015`` to ``vs2017`` Transition
 

src/maintainer/maintainer_faq.rst

@@ -146,7 +146,7 @@ FAQ
 :ref:`(Q) <mfaq_contact_core>` **How can I contact conda-forge/core?**
 
   When in an issue or PR, you can contact `conda-forge/core <https://conda-forge.org/docs/orga/governance.html#teams-roles>`__ by simply mentioning ``@conda-forge/core`` in a comment.
-  If you don't receive an an answer after a couple of days, feel free to reach out to us via the public `element <https://app.element.io/#/room/#conda-forge:matrix.org>`__ chatroom.
+  If you don't receive an an answer after a couple of days, feel free to reach out to us via the public `Element <https://app.element.io/#/room/#conda-forge:matrix.org>`__ chatroom.
 
   .. note::
 

src/maintainer/updating_pkgs.rst

@@ -168,7 +168,7 @@ We need to re-render when there are changes in the following parts of the feedst
 - ``yum_requirements.txt`` or ``conda-forge.yml``.
 - Updates in the build matrix due to new versions of Python, NumPy, PERL, R, etc.
 - Updates in conda-forge pinning that affect the feedstock.
-- Build issues that a feedstock configuration update will fix (follow us on `element <https://app.element.io/#/room/#conda-forge:matrix.org>`_ to know about those).
+- Build issues that a feedstock configuration update will fix (follow us on `Element <https://app.element.io/#/room/#conda-forge:matrix.org>`_ to know about those).
 
 Updating for newly released Python version
 ==========================================
@@ -286,7 +286,7 @@ an issue in the feedstock repository with the following title:
 
 where ``username`` is the username of the new maintainer to be added.
 A PR will be automatically created and a maintainer or a member of the ``core`` team, in case no maintainer is active anymore, can then merge this PR to add the user. 
-To contact core, ping them by mentioning @conda-forge/core in a comment or, if you haven't heard back in a while or are new to conda-forge, contact them through the community `element <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
+To contact core, ping them by mentioning @conda-forge/core in a comment or, if you haven't heard back in a while or are new to conda-forge, contact them through the community `Element <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 
 .. note::
 

src/orga/joining-the-team.rst

@@ -19,7 +19,7 @@ for officially interfacing with external communities, organizations, non-profits
 and companies. They are also responsible for maintaining conda-forge's infrastructure.
 
 If you are interested in joining the core team, please get in touch with us on our
-`Element Chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
+`Element chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 Core members are added via a vote amongst the current core team. The core team
 member who is running your vote will ask you to provide sufficient justification
 as to why you should be nominated to core. Prior service to the community, including
@@ -46,7 +46,7 @@ Generally speaking, your role is as follows:
 4. Helping recipe maintainers who bump the ``conda-forge/help-*`` teams.
 
 To join the staged-recipes team, please ask one of the core members on our
-`Element Chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
+`Element chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 We will then reach consensus in private and let you know our decision.
 Our decision will likely be "yes" but it could be "please get more involved
 with the review process on staged recipes first" if we have not seen you

src/user/announcements.rst

@@ -13,7 +13,7 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
 
 We have made the ``conda-forge`` Google Group read-only. Please use the new 
 ``conda-forge`` `discourse forum <https://conda.discourse.group/c/pkg-building/conda-forge/25>`_, 
-our `Element Chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`_, or it's `Matrix/Element 
+our `Gitter room <https://gitter.im/conda-forge/conda-forge.github.io>`_, , or it's `Matrix/Element 
 counterpart <https://app.element.io/#/room/#conda-forge-space:matrix.org>`_ instead.
 
 
@@ -313,7 +313,7 @@ We have now completed rolling out the new staging process for uploads
 to anaconda.org. Direct uploads to the ``conda-forge`` channel will no
 longer work. If you are having trouble with package uploads, please
 rerender your feedstock with the latest version of ``conda-smithy``.
-As always, if you need help, bump us on Element chatroom or GitHub!
+As always, if you need help, bump us on gitter or GitHub!
 
 
 2020-08-06: Fixed Maintenance Process for Feedstock Teams
@@ -476,7 +476,7 @@ What will you see as a feedstock maintainer?
 
 Despite our extensive testing, we do not expect this change to be completely smooth,
 so please bear with us. As always, if you have any questions, concerns, or trouble, you
-can find us on Element chatroom or bump us directly on Github!
+can find us on gitter or bump us directly on Github!
 
 
 2020-03-24: ``vs2015`` to ``vs2017`` Transition