standardize to lowercase, no-backticks by default

Author: jaimergp

src/contracting/00_intro.rst

@@ -1,9 +1,9 @@
 Contracting Information
 #######################
 
-If you are interested in a contractual engagement to solve a specific problem that you're facing, this page details the kinds of services that are available to you. ``conda-forge``, as an entity, does not have the ability to engage in a contractual arrangement as of now.
+If you are interested in a contractual engagement to solve a specific problem that you're facing, this page details the kinds of services that are available to you. conda-forge, as an entity, does not have the ability to engage in a contractual arrangement as of now.
 However, there are a number of community members that you may engage with. 
-``conda-forge`` does not endorse anyone (individuals or companies) listed on this page.
+conda-forge does not endorse anyone (individuals or companies) listed on this page.
 
 
 If you are interested in a service that is not listed on this page, please reach out to us on our `issue tracker <https://github.com/conda-forge/conda-forge.github.io/issues>`__, on  `Element <https://app.element.io/#/room/#conda-forge:matrix.org>`__  or via emailing the core team directly at [email protected] and we will help to circulate your request more broadly within the community.
@@ -39,7 +39,7 @@ Background / Description: Quansight's goal is to create operational solutions to
 Becoming a Service Provider
 ***************************
 
-The ``conda-forge`` core team reserves the right to unilaterally update this list at any time for any reason.
+The conda-forge core team reserves the right to unilaterally update this list at any time for any reason.
 If you are a service provider and are interested in being added to this list please open up a pull request against the conda-forge.github.io repository.
 Add yourself to this list and detailing the services you provide. 
 Please be brief and link to existing materials on your own website where possible.

src/index.rst

@@ -13,7 +13,7 @@ Chances are we have already packaged it for you. You can `search <https://anacon
 
 **Cannot find a package or only outdated versions of a package?** - Everybody is welcome to contribute to our package stack!
 
-- We value all kinds of contributions — not just code. A few recommended ways to start contributing to ``conda-forge`` are:
+- We value all kinds of contributions — not just code. A few recommended ways to start contributing to conda-forge are:
 
  - `Contribute new packages <https://conda-forge.org/docs/maintainer/adding_pkgs.html>`__
  - Help update and `maintain packages <https://conda-forge.org/docs/maintainer/updating_pkgs.html#maintaining-pkgs>`__

src/maintainer/adding_pkgs.rst

@@ -51,7 +51,7 @@ Your final recipe should have no comments (unless they're actually relevant to t
 
 .. note::
 
-  If there are any details you are not sure about please create a pull request anyway. The ``conda-forge`` team will review it and help you make changes to it.
+  If there are any details you are not sure about please create a pull request anyway. The conda-forge team will review it and help you make changes to it.
 
 In case you are building your first recipe using conda-forge, a step-by-step instruction and checklist that will help you with a successful build is provided below.
 
@@ -96,7 +96,7 @@ Checklist
 
 * Ensure that the license and license family descriptors (optional) have the right case and that the license is correct. Note that case sensitive inputs are required (e.g. Apache-2.0 rather than APACHE 2.0). Using SPDX identifiers for license field is recommended. (see :ref:`spdx`)
 * Ensure that you have included a license file if your license requires one -- most do. (see `here <https://github.com/conda-forge/staged-recipes/blob/a504af81c05491bf7b0b018b2fa1efe64767985c/recipes/example/meta.yaml#L52-L55>`_)
-* In case your project has tests included, you need to decide if these tests should be executed while building the ``conda-forge`` feedstock.
+* In case your project has tests included, you need to decide if these tests should be executed while building the conda-forge feedstock.
 * Make sure that all tests pass successfully at least on your development machine.
 * Recommended: run the test locally on your source code to ensure the recipe works locally (see  :ref:`staging_test_locally`).
 * Make sure that your changes do not interfere with other recipes that are in the ``recipes`` folder (e.g. the ``example`` recipe).
@@ -121,7 +121,7 @@ Post staging process
 
 * After the PR is merged, our :term:`CI` services will create a new git repo automatically. For example, the recipe for a package named ``pydstool`` will be moved to a new repository `https://github.com/conda-forge/pydstool-feedstock <https://github.com/conda-forge/pydstool-feedstock>`_. This process is automated through a CI job on the ``conda-forge/staged-recipes`` repo. It sometimes fails due to API rate limits and will automatically retry itself. If your feedstock has not been created after a day or so, please get in touch with the ``conda-forge/core`` team for help.
 * CI services will be enabled automatically and a build will be triggered automatically which will build the conda package and upload to `https://anaconda.org/conda-forge <https://anaconda.org/conda-forge>`_
-* If this is your first contribution, you will be added to the ``conda-forge`` `team <https://github.com/orgs/conda-forge/people>`_ and given access to the CI services so that you can stop and restart builds. You will also be given commit rights to the new git repository.
+* If this is your first contribution, you will be added to the conda-forge `team <https://github.com/orgs/conda-forge/people>`_ and given access to the CI services so that you can stop and restart builds. You will also be given commit rights to the new git repository.
 * If you want to make a change to the recipe, send a :term:`PR` to the git repository from a fork. Branches of the main repository are used for maintaining different versions only.
 
 
@@ -237,7 +237,7 @@ It defines everything that is required to build and use the package.
 
 A full reference of the structure and fields of ``meta.yaml`` file can be found in the `Defining metadata (meta.yaml) <https://conda.io/projects/conda-build/en/stable/resources/define-metadata.html>`__ section in the conda-build documentation.
 
-In the following, we highlight particularly important and ``conda-forge`` specific information and guidelines, ordered by section in ``meta.yaml``.
+In the following, we highlight particularly important and conda-forge specific information and guidelines, ordered by section in ``meta.yaml``.
 
 
 Source
@@ -270,7 +270,7 @@ install the necessary tools below).
 
 To generate the ``sha256`` hash: ``openssl sha256 your_sdist.tar.gz``
 
-You may need the openssl package, available on ``conda-forge``
+You may need the openssl package, available on conda-forge
 ``conda install openssl -c conda-forge``.
 
 .. tip::
@@ -403,13 +403,13 @@ For a detailed explanation please refer to the `conda-build documentation <https
 Avoid external dependencies
 ...........................
 
-As a general rule: all dependencies have to be packaged by ``conda-forge`` as well. This is necessary to assure :term:`ABI` compatibility for all our packages.
+As a general rule: all dependencies have to be packaged by conda-forge as well. This is necessary to assure :term:`ABI` compatibility for all our packages.
 
 There are only a few exceptions to this rule:
 
 #. Some dependencies have to be satisfied with :term:`CDT` packages (see :ref:`cdt_packages`).
 
-#. Some packages require root access (e.g. device drivers) that cannot be distributed by ``conda-forge``. These dependencies should be avoided whenever possible.
+#. Some packages require root access (e.g. device drivers) that cannot be distributed by conda-forge. These dependencies should be avoided whenever possible.
 
 
 
@@ -513,7 +513,7 @@ Sometimes defining tests seems to be hard, e.g. due to:
  - test suites may take too long to run on limited :term:`CI` infrastructure.
  - tests may take too much bandwidth.
 
-In these cases, ``conda-forge`` may not be able to execute the prescribed test suite.
+In these cases, conda-forge may not be able to execute the prescribed test suite.
 
 However, this is no reason for the recipe to not have tests. At the very least,
 we want to verify that the package has installed the desired files in the desired

src/maintainer/conda_forge_yml.rst

@@ -1,7 +1,7 @@
 Configuring conda-forge.yml
 ***************************
 
-You can configure how ``conda-forge`` is set up and built via the ``conda-forge.yml``
+You can configure how conda-forge is set up and built via the ``conda-forge.yml``
 file that is present in the root directory of a feedstock.
 
 Rerendering the feedstock after you modify this file is usually required and always a good idea (see :ref:`dev_update_rerender`).
@@ -165,7 +165,7 @@ Leaving this field empty implicitly requests to build a package natively. i.e.
 
 build_with_mambabuild
 ---------------------
-This option, when enabled, configures the ``conda-forge`` CI to run a debug build using the ``mamba`` solver. Check `this <https://conda-forge.org/docs/maintainer/maintainer_faq.html#mfaq-mamba-local>`__ to know more.
+This option, when enabled, configures the conda-forge CI to run a debug build using the ``mamba`` solver. Check `this <https://conda-forge.org/docs/maintainer/maintainer_faq.html#mfaq-mamba-local>`__ to know more.
 
 .. code-block:: yaml
 
@@ -254,7 +254,7 @@ artifacts. The currently supported options are
 conda_forge_output_validation
 -----------------------------
 
-This field must be set to ``True`` for feedstocks in the ``conda-forge`` GitHub
+This field must be set to ``True`` for feedstocks in the conda-forge GitHub
 organization. It enables the required feedstock artifact validation as described
 in :ref:`output_validation`.
 
@@ -455,7 +455,7 @@ The relative path to the recipe directory. The default is:
 remote_ci_setup
 ---------------
 This option can be used to override the default ``conda-forge-ci-setup`` package.
-Can be given with ``${url or channel_alias}::package_name``, defaults to ``conda-forge``
+Can be given with ``${url or channel_alias}::package_name``, defaults to conda-forge
 channel_alias if no prefix is given.
 
 .. code-block:: yaml

src/maintainer/infrastructure.rst

@@ -9,13 +9,13 @@ Repositories
 Staging area for recipes
 ------------------------
 
-`conda-forge/staged-recipes <https://github.com/conda-forge/staged-recipes>`__ is the entry point for new packages to join the ``conda-forge`` package collection.
+`conda-forge/staged-recipes <https://github.com/conda-forge/staged-recipes>`__ is the entry point for new packages to join the conda-forge package collection.
 You can find the detailed guide for submitting new package recipes in :ref:`creating_recipes`.
 
 Smithy
 ------
 
-Smithy contains maintenance code for ``conda-forge``, which is used by the ``conda-smithy`` command line tool and the :ref:`dev_admservice`. Smithy lives in the repository `conda-forge/conda-smithy <https://github.com/conda-forge/conda-smithy>`_.
+Smithy contains maintenance code for conda-forge, which is used by the ``conda-smithy`` command line tool and the :ref:`dev_admservice`. Smithy lives in the repository `conda-forge/conda-smithy <https://github.com/conda-forge/conda-smithy>`_.
 
 ``conda-forge/conda-smithy`` is the right repository to report bugs for
 
@@ -25,15 +25,15 @@ Smithy contains maintenance code for ``conda-forge``, which is used by the ``con
 
 ``conda-smithy`` also contains the command line tool that you should use if you rerender manually from the command line (see :ref:`dev_update_rerender`).
 
-Smithy can be used beyond ``conda-forge``'s purposes. For example, it can be used to `set up self-hosted Azure agents <azure-config>` for non-``conda-forge`` infrastructures.
+Smithy can be used beyond conda-forge's purposes. For example, it can be used to `set up self-hosted Azure agents <azure-config>` for non-conda-forge infrastructures.
 (You could also consider using `Azure virtual machine scale set agents <https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/scale-set-agents?view=azure-devops>`_,
 which could be less expensive to run than permanently active agents.)
 
 
 Web services
 ------------
 
-The Heroku app providing the ``conda-forge`` web services lives in `conda-forge/conda-forge-webservices <https://github.com/conda-forge/conda-forge-webservices>`__.
+The Heroku app providing the conda-forge web services lives in `conda-forge/conda-forge-webservices <https://github.com/conda-forge/conda-forge-webservices>`__.
 Please note that the code logic provided by the app is in the ``Smithy`` repository.
 
 Bugs or suggestions regarding the service functionality should therefore be opened in ``conda-forge/conda-smithy``'s `bug tracker <https://github.com/conda-forge/conda-smithy/issues>`__.
@@ -43,7 +43,7 @@ conda-forge pinning
 
 Package-wide dependency pins are defined in `conda_build_config.yaml <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml>`__ in the `conda-forge/conda-forge-pinning-feedstock <https://github.com/conda-forge/conda-forge-pinning-feedstock>`_.
 
-For more information on ``conda-forge`` wide package pins, please refer to :ref:`globally_pinned_packages`.
+For more information on conda-forge wide package pins, please refer to :ref:`globally_pinned_packages`.
 
 Please open a :term:`PR` and/or an issue there, if you think a pin needs to be advanced. For more information on updating globally pinned packages, please refer to :ref:`update_pins`.
 
@@ -63,7 +63,7 @@ If you found any typo error, unclear explanations or new topics that can be cove
 Admin web services
 ==================
 
-``conda-forge`` is running a webservice on Heroku called `conda-forge-webservices <https://github.com/conda-forge/conda-forge-webservices>`_.
+conda-forge is running a webservice on Heroku called `conda-forge-webservices <https://github.com/conda-forge/conda-forge-webservices>`_.
 
 The following services are run by default on a feedstock:
 
@@ -117,14 +117,14 @@ all of the CI builds to restart.
 ------------------------------------
 
 Entering this command in the PR of a feedstock or staged-recipes will have the admin bot @-mention the team
-associated with the repo. This command can be useful for people who are not yet members of ``conda-forge`` and
+associated with the repo. This command can be useful for people who are not yet members of conda-forge and
 so cannot @-mention the ``staged-recipes`` team for PR reviews.
 
 @conda-forge-admin, please ping conda-forge/<team>
 --------------------------------------------------
 
 Entering this command in the PR of a feedstock or staged-recipes will have the admin bot @-mention the respective team.
-This command can be useful for people who are not yet members of ``conda-forge`` and
+This command can be useful for people who are not yet members of conda-forge and
 so cannot @-mention someone due to the general GitHub limitations.
 
 @conda-forge-admin, please rerun bot
@@ -169,7 +169,7 @@ changes. The rest of the contents will be added in a subsequent commit after a f
 CI build services
 =================
 
-Here we describe common issues with the CI Services that ``conda-forge`` builds.
+Here we describe common issues with the CI Services that conda-forge builds.
 
 Azure Pipelines
 ---------------
@@ -270,16 +270,16 @@ To skip a CI build for a given commit, put ``[ci skip] ***NO_CI***`` in the comm
 Third-party Use of Our CI Services
 ----------------------------------
 
-Due to its stature in the open-source community, ``conda-forge`` has enhanced access to certain CI services. This access is a community
-resource entrusted to ``conda-forge`` for use in building packages. We thus cannot support third-party or "off-label" CI jobs in our
+Due to its stature in the open-source community, conda-forge has enhanced access to certain CI services. This access is a community
+resource entrusted to conda-forge for use in building packages. We thus cannot support third-party or "off-label" CI jobs in our
 feedstocks on any of our CI services. If we find such use, we will politely ask the maintainers to rectify the situation. We may
 take more serious actions, including archiving feedstocks or removing maintainers from the organization, if the situation cannot be rectified.
 
 
 Compilers and Runtimes
 ======================
 
-``conda-forge`` builds and maintains its own set of compilers for various languages
+conda-forge builds and maintains its own set of compilers for various languages
 and/or systems (e.g., ``C``, ``FORTRAN``, ``C++``, ``CUDA``, etc.). These are used
 in all of our CI builds to build both core dependencies (e.g., ``Python``) and maintainer-contributed
 packages. While we do not have any formal policies or promises of support for these
@@ -343,7 +343,7 @@ works as follows.
    and some information about the package it is trying to upload.
 3. The webservices server validates the secret token, the integrity of the package, and
    that the package is allowed for the given feedstock.
-4. If all of the validation passes, the package is then copied to the ``conda-forge``
+4. If all of the validation passes, the package is then copied to the conda-forge
    channel.
 
 We attempt to report errors in this process to users via comments on commits/issues in the feedstocks.