docs: Clean up documentation. (#1025)

- Removed out of date known issues.
- Cleaned up workflow commands.
- Removed references to out of date Pycharm instructions.

Author: dianakhuang

README.rst

@@ -365,15 +365,6 @@ Some common service combinations include:
 .. _analyticsapi: https://github.com/openedx/edx-analytics-data-api
 
 
-Known Issues
-------------
-
-Currently, some containers rely on Elasticsearch 7 and some rely on Elasticsearch 1.5. This is
-because services are in the process of being upgraded to Elasticsearch 7, but not all of them
-support Elasticsearch 7 yet. As we complete these migrations, we will update the dependencies
-of these containers.
-
-
 
 Advanced Configuration Options
 ------------------------------
@@ -411,7 +402,6 @@ As a specific example, if ``OPENEDX_RELEASE`` is set in your environment as ``ju
 .. _edx-e2e-tests README: https://github.com/edx/edx-e2e-tests/#how-to-run-lms-and-studio-tests
 .. _edxops Docker image: https://hub.docker.com/r/edxops/
 .. _Docker Hub: https://hub.docker.com/
-.. _Pycharm Integration documentation: docs/pycharm_integration.rst
 .. _devpi documentation: docs/devpi.rst
 .. _edx-platform testing documentation: https://github.com/openedx/edx-platform/blob/master/docs/guides/testing/testing.rst#running-python-unit-tests
 .. |Build Status provisioning| image:: https://github.com/openedx/devstack/actions/workflows/provisioning-tests.yml/badge.svg?branch=master

docs/devstack_faq.rst

@@ -286,10 +286,6 @@ After changing settings, you can restart the LMS/Studio process without restarti
    make dev.restart-devserver.lms     # For LMS
    make dev.restart-devserver.studio  # For Studio/CMS
 
-How do I integrate with PyCharm?
---------------------------------
-
-See the `Pycharm Integration documentation`_.
 
 What is DevPI and how does it affect Devstack?
 ----------------------------------------------
@@ -304,5 +300,4 @@ See the `devpi documentation`_.
 .. _Changing Themes for an Open edX Site: https://edx.readthedocs.io/projects/edx-installing-configuring-and-running/en/latest/configuration/changing_appearance/theming/index.html
 .. _updating relational database dumps: docs/database-dumps.rst
 .. _Django Migration Don'ts: https://engineering.edx.org/django-migration-donts-f4588fd11b64
-.. _Pycharm Integration documentation: docs/pycharm_integration.rst
 .. _devpi documentation: docs/devpi.rst

docs/workflow.rst

@@ -14,8 +14,8 @@ These instructions are written using the LMS as an example. Replace ``lms`` with
 #. Activate your devstack virtualenv. See the main Getting Started instructions if you don't already have one.
 #. Launch your service in a clean state:
 
-   #. Run ``make lms-down lms-pull lms-up`` to halt any running services and remove their containers, pull the latest disk images, and launch your service.
-   #. Optionally, watch ``make lms-logs`` to follow the logs. This lets you see when the service finishes coming up, and prints the port it is listening on.
+   #. Run ``make dev.remove-containers dev.pull.lms dev.up.lms`` to halt any running services and remove their containers, pull the latest disk images, and launch your service.
+   #. Optionally, watch ``make dev.logs.lms`` to follow the logs. This lets you see when the service finishes coming up, and prints the port it is listening on.
 
       - Your service is up when you see a block of messages that looks like the following::
 
@@ -25,15 +25,15 @@ These instructions are written using the LMS as an example. Replace ``lms`` with
           edx.devstack.lms                  | Starting development server at http://0.0.0.0:18000/
           edx.devstack.lms                  | Quit the server with CONTROL-C.
 
-      - If the logs show warning messages about missing tables or needed migrations, run ``make lms-migrate`` and then continue
+      - If the logs show warning messages about missing tables or needed migrations, run ``make dev.migrate.lms`` and then continue
 
-      - If there are complaints about import failures, Python package requirements may have changed since the last disk image. Run ``make lms-shell`` and then ``make requirements`` from inside the shell, then restart the service with ``make lms-restart-devserver``.
+      - If there are complaints about import failures, Python package requirements may have changed since the last disk image. Run ``make lms-shell`` and then ``make requirements`` from inside the shell, then restart the service with ``make dev.restart-devserver.lms``.
 
 #. Your service should now be up and accessible, and you can develop in your IDA's repo. When you make changes on disk, a file watcher will restart the service in devstack. It may take a moment for the service to come back up with your changes.
 
-   - For some changes, this auto-restarting is insufficient, and you'll need to make a change from inside ``make lms-shell`` (such as ``make requirements`` or a migrations or other management command) and then run ``make lms-restart-devserver`` from the outside.
+   - For some changes, this auto-restarting is insufficient, and you'll need to make a change from inside ``make lms-shell`` (such as ``make requirements`` or a migrations or other management command) and then run ``make dev.restart-devserver.lms`` from the outside. Running ``make dev.restart-devserver.lms`` may also fix issues if the runserver command is not restarting automatically after code changes.
 
-#. When you're done, you can either run ``make lms-stop`` to shut down the service but leave the container intact (with requirements installations and other file changes preserved) or ``make lms-down`` to destroy the containers as well.
+#. When you're done, you can run ``make dev.stop.lms`` to shut down the service but leave the container intact (with requirements installations and other file changes preserved).
 
 Variations
 ----------