Edit content to bring more up to date

Author: willingc

docs/community/community-guide.md

@@ -8,20 +8,25 @@ team!
 
 There are a few resources that are particularly useful for team members. Here's
 a quick list to get you started.
-- devguide
-- docs
+
+- [devguide](https://devguide.python.org)
+- [docs](https://docs.python.org)
 - python_docs_theme
 - discourse channel
-
+- discord channel
 
 ### General information about communication channels
 
 We are trying to organize our discussions in order to help both contributors and
 maintainers find and choose the right communication channels and have a positive experience :-)
 
 In this respect, we are using:
-1. [BPO](https://bugs.python.org) and GitHub issues for specific discussions related to changing a repository's content. This is determined by doc project.
+
+1. GitHub issues for specific discussions related to changing a repository's content.
 2. The [Discourse forum](http://discuss.python.org/) for general discussions, support
 questions, or just as a place where we can inspire each other.
 
 ## How can I help?
+
+Read the devguide's section on documentation.
+Visit the Python repo's GitHub issues and look for issues tagged with `docs`.

docs/community/index.rst

@@ -18,4 +18,3 @@ The Documentation Community Team has a Code of Conduct
     contributing
     community-guide
     skills
-    team

docs/community/skills.md

@@ -4,24 +4,13 @@
 
 The short answer to this question is: follow your interests :-)
 
-## A few general ways to help out
-
-
-### Python-specific knowledge
-
-- **Code structure of the docs repository**
+The [Python Developer's Guide documentation](https://devguide.python.org/documentation) section is a good place to start.
+It's a comprehensive guide to the Python documentation and the tools we use to build it.
+It's a good idea to read through the guide to get a sense of the tools and processes we use.
 
 ## A note on complexity of tasks
 
 Depth/expertise required for certain kinds of tasks can be hard to nail down and not at
 all obvious. If you'd like to make a contribution and you're not sure where to start,
 a good rule of thumb is to reach out to another team member to help
 you scope the work you'd like to do, and to set expectations.
-
-## Links
-
-
-
-## Resources for Learning
-
-In this section, we gather some introductory materials for learning the aforementioned tools.

docs/community/team.rst

@@ -1,3 +1,7 @@
+:orphan:
+
+.. This page is retained solely for existing links.
+
 .. _doc_team:
 
 ==================

docs/editorial-board/index.rst

@@ -4,8 +4,7 @@
 Editorial Board
 ===============
 
-The acceptance of `PEP 732 <https://peps.python.org/pep-0732/>`_ established
-the Python Documentation Editorial Board.
+The acceptance of :pep:`732` established the Python Documentation Editorial Board.
 
 Monthly Editorial Board Meetings
 ================================

docs/monthly-meeting/index.rst

@@ -5,7 +5,7 @@ Monthly Reports Archive
 
 `Current agenda <https://hackmd.io/@encukou/pydocswg1>`_
 
-Monthly reports in reverse chronological order.
+Monthly reports in chronological order.
 
 .. toctree::
    :maxdepth: 1