Follow conda capitalization standards (mantidproject#39522)

Author: thomashampson

CMakePresets.json

@@ -8,7 +8,7 @@
   "configurePresets": [
     {
       "name": "conda",
-      "description": "Inherited by all Conda-based, non-hidden presets",
+      "description": "Inherited by all conda-based, non-hidden presets",
       "hidden": true,
       "binaryDir": "${sourceDir}/build",
       "generator": "Ninja",
@@ -28,7 +28,7 @@
     },
     {
       "name": "unix-debug",
-      "description": "Inherited by all Unix-like presets for debugging. Overrides Conda CXX flags for debugging",
+      "description": "Inherited by all Unix-like presets for debugging. Overrides conda CXX flags for debugging",
       "hidden": true,
       "cacheVariables": {
         "CMAKE_CXX_FLAGS_DEBUG": "-g -Og",

buildconfig/CMake/WindowsSetup.cmake

@@ -56,7 +56,7 @@ else()
   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /Zm${VISUALSTUDIO_COMPILERHEAPLIMIT}")
 endif()
 
-# Define a new configuration for debugging with Conda. Crucially it must link to the MSVC release runtime but we switch
+# Define a new configuration for debugging with conda. Crucially it must link to the MSVC release runtime but we switch
 # off all optimzations
 set(_conda_debug_cfg_name DebugWithRelRuntime)
 string(TOUPPER ${_conda_debug_cfg_name} _conda_debug_cfg_name_upper)
@@ -91,7 +91,7 @@ set(CMAKE_CONFIGURATION_TYPES
 )
 message(
   STATUS
-    "Detected a build with Conda on Windows. Resetting available build configurations to ${CMAKE_CONFIGURATION_TYPES}"
+    "Detected a build with conda on Windows. Resetting available build configurations to ${CMAKE_CONFIGURATION_TYPES}"
 )
 
 # HDF5 uses threads::threads target

buildconfig/Jenkins/Conda/download-and-install-mambaforge

@@ -55,7 +55,7 @@ if [ ! -f $EXPECTED_MAMBA_EXE ]; then
         elif [ -x "$(which wget)" ] ; then
             wget $URL
         else
-            echo "Could not download Conda as wget and curl are not installed."
+            echo "Could not download conda as wget and curl are not installed."
             exit 1
         fi
     fi
@@ -75,7 +75,7 @@ if [ ! -f $EXPECTED_MAMBA_EXE ]; then
     if [[ $OSTYPE == 'msys'* ]]; then
         # Replace all / with \ for windows batch support before passing in $EXPECTED_MAMBAFORGE_PATH
         cmd.exe //C "START /wait "" $MAMBAFORGE_SCRIPT_NAME /InstallationType=JustMe /S /D=${EXPECTED_MAMBAFORGE_PATH////\\}"
-        # The paths in the Conda environment shell environments are Windows style. Convert to cygwin style
+        # The paths in the conda environment shell environments are Windows style. Convert to cygwin style
         cp $EXPECTED_MAMBAFORGE_PATH/etc/profile.d/conda.sh{,.orig}
         cat $EXPECTED_MAMBAFORGE_PATH/etc/profile.d/conda.sh.orig | \
           sed -e '/^export\ CONDA_/s/\\/\//g' | \

dev-docs/source/CodeCoverage.rst

@@ -1,5 +1,5 @@
 ========================
-Generating Code Coverage
+Generating code coverage
 ========================
 
 .. contents::
@@ -16,14 +16,14 @@ GCC and LLVM have tooling built in to allow a developer to view the code coverag
 
 This will work for native C++ code and any code executed via Python, as the instrumentation is compiled into the binary output. Gcovr will also filter out any non-project code automatically.
 
-Coverage on Conda
+Coverage on conda
 #################
 
-Since the move to `conda`, `GCC` is installed through the conda package `gxx_linux-64`. This conda package does NOT include `gcov`, required to assess code coverage. `gcov` is not currently available on `conda`, so you will need to ensure that `gcov` can be instead found on your system, and that this version of `gcov` is the same version as the `GCC` compiler we install using `conda`. If this is not the case, errors will be raised during the generation of coverage data.
+Since the move to conda, `GCC` is installed through the conda package `gxx_linux-64`. This conda package does NOT include `gcov`, required to assess code coverage. `gcov` is not currently available on conda, so you will need to ensure that `gcov` can be instead found on your system, and that this version of `gcov` is the same version as the `GCC` compiler we install using conda. If this is not the case, errors will be raised during the generation of coverage data.
 
 As `gcov` is packaged with `GCC`, you will need to install `GCC` on your system. You can typically do this using the `apt` package manager. If an appropriate version of `GCC` is not available for your OS you will unfortunately have to build it from source: https://gcc.gnu.org/wiki/InstallingGCC
 
-C++ Specific Notes
+C++ specific notes
 ##################
 
 The coverage target(s) do not run the tests automatically. Users must either run the test(s) or file(s) they are interested in manually for data to be produced by the tooling.

dev-docs/source/CondaPackageManager.rst

@@ -7,8 +7,8 @@ Conda Package Manager
 .. contents::
    :local:
 
-Mantid uses `Conda <https://docs.conda.io/en/latest/>`_ as its package management system. This document gives a
-developer overview on how we use the Conda package manager, including tips on how to debug dependency issues, and
+Mantid uses `conda <https://docs.conda.io/en/latest/>`_ as its package management system. This document gives a
+developer overview on how we use the conda package manager, including tips on how to debug dependency issues, and
 our policy towards using ``pip`` packages (it is strongly discouraged).
 
 Creating Environments
@@ -48,12 +48,12 @@ Finding a broken dependency
 ---------------------------
 
 The nightly pipelines can sometimes fail for obscure reasons, seemingly unrelated to the changes made within
-Mantid. In this case, it is probable that a Conda dependency has updated, and the new update is "Broken"
+Mantid. In this case, it is probable that a conda dependency has updated, and the new update is "Broken"
 (if it is a minor or patch update) or no longer compatible with Mantid (if it is a major update).
 
 To find the dependency which has changed, you can run the ``tools/Jenkins/dependency_spotter.py`` script. This
 script takes two Jenkins build numbers, and optionally the OS label, the pipeline name, and the name of the file to
-compare. It will then output the changes in Conda package versions used in the two builds, if there are any. A
+compare. It will then output the changes in conda package versions used in the two builds, if there are any. A
 few examples on how to use it:
 
 .. code-block:: sh
@@ -71,7 +71,7 @@ Another useful command for investigating the dependencies of specific packages i
 Fixing a broken dependency
 --------------------------
 
-After identifying the Conda dependency and version which is causing the unwanted behaviour, there are several
+After identifying the conda dependency and version that is causing the unwanted behaviour, there are several
 options we can take to fix the issue. The following options are in order of preference:
 
 1. Raise an issue in the dependencies `feedstock <https://conda-forge.org/docs/maintainer/adding_pkgs.html#feedstock-repository-structure>`_
@@ -91,18 +91,18 @@ follows:
 
 .. code-block:: none
 
-  We strongly encourage PyPi dependencies be built into Conda packages and uploaded to conda-forge. PyPi packages
-  will not be automatically installed into our Mantid Conda environments, and should instead be installed by
+  We strongly encourage PyPi dependencies be built into conda packages and uploaded to conda-forge. PyPi packages
+  will not be automatically installed into our Mantid conda environments, and should instead be installed by
   users of the software, if required.
 
-We do not want to include pip packages as dependencies in our Conda recipes because there is no guarantee of
-compatibility between the two package managers. In the past, attempting to resolve compatibile package versions
+We do not want to include pip packages as dependencies in our conda recipes because there is no guarantee of
+compatibility between the two package managers. In the past, attempting to resolve compatible package versions
 when two package managers are involved have caused broken Mantid installations. Furthermore, the original
-motivation for moving towards Conda was so that we had a unified package manager rather than using several
+motivation for moving towards conda was so that we had a unified package manager rather than using several
 different systems or mechanisms. Including pip packages in our dependencies would be a backwards step.
 
 The other solution we considered was installing our pip dependencies downstream within our DAaaS workspace
 configuration repository. We decided against this because it feels like bad practise to have a formalised
 way of installing dependencies of a software in a way which is completely detached. The prevailing message is
-this: please only use Conda packages. We provide :ref:`pip install instructions <pip-install-ref>` for users if
+this: please only use conda packages. We provide :ref:`pip install instructions <pip-install-ref>` for users if
 they would like to take the risk.

dev-docs/source/GettingStarted/GettingStarted.rst

@@ -18,8 +18,8 @@ Getting Started
 Environment Setup
 #################
 
-With the addition of Conda to our workflow we at present have two different methods of Getting Started with mantid development.
-Therefore you can choose which method to setup with (We recommend Conda as it will be the only supported
+With the addition of conda to our workflow we at present have two different methods of Getting Started with mantid development.
+Therefore you can choose which method to setup with (We recommend conda as it will be the only supported
 method eventually).
 
 * :ref:`GettingStartedCondaWindows`

dev-docs/source/GettingStarted/GettingStartedCondaLinux.rst

@@ -1,7 +1,7 @@
 .. _GettingStartedCondaLinux:
 
 ===========================
-Develop with Conda on Linux
+Develop with conda on Linux
 ===========================
 
 Install Git
@@ -58,7 +58,7 @@ Building and debugging with CLion
 ---------------------------------
 Please follow the Linux related instructions on :ref:`this page <clion-ref>`.
 
-CMake Conda variables
+CMake conda variables
 -----------------------
 The `CONDA_BUILD` parameter is used to customise our installation, which is required when we are using the conda-build tool to build and package Mantid. This option can be passed to CMake on the command line using -DCONDA_BUILD=True.
 

dev-docs/source/GettingStarted/GettingStartedCondaOSX.rst

@@ -1,7 +1,7 @@
 .. _GettingStartedCondaOSX:
 
 ===========================
-Develop with Conda on MacOS
+Develop with conda on MacOS
 ===========================
 
 Install `Git <https://git-scm.com/>`_
@@ -42,7 +42,7 @@ How to build
 * To build Mantid Workbench use: ``ninja``
 * To build Unit Tests use: ``ninja AllTests``
 
-CMake Conda variables
+CMake conda variables
 -----------------------
 The ``CONDA_BUILD`` parameter is used to customise our installation, which is required when we are using the conda-build tool to build and package Mantid.
 This option can be passed to CMake on the command line using ``-DCONDA_BUILD=True``.

dev-docs/source/GettingStarted/GettingStartedCondaWindows.rst

@@ -1,7 +1,7 @@
 .. _GettingStartedCondaWindows:
 
 =============================
-Develop with Conda on Windows
+Develop with conda on Windows
 =============================
 
 Install `Visual Studio 2022 Community Edition <https://visualstudio.microsoft.com/downloads/>`_
@@ -39,7 +39,7 @@ Install `Mambaforge <https://github.com/conda-forge/miniforge/releases>`_
 -------------------------------------------------------------------------
 
 * Choose the latest version of ``Mambaforge-Windows-x86_64.exe``
-* Run your downloaded ``Mambaforge-Windows-x86_64.exe`` and work through the installer until it finishes. In order to make it easier later on, check the box that adds Conda to your path.
+* Run your downloaded ``Mambaforge-Windows-x86_64.exe`` and work through the installer until it finishes. In order to make it easier later on, check the box that adds conda to your path.
 
 Setup the mantid conda environment
 ----------------------------------
@@ -95,6 +95,6 @@ Building and debugging with CLion
 ---------------------------------
 Please follow the Windows related instructions on :ref:`this page <clion-ref>`.
 
-CMake Conda variables
+CMake conda variables
 ---------------------
 The `CONDA_BUILD` parameter is used to customise our installation, which is required when we are using the conda-build tool to build and package Mantid. This option can be passed to CMake on the command line using -DCONDA_BUILD=True.

dev-docs/source/GettingStarted/GettingStartedNoneConda.rst

@@ -1,7 +1,7 @@
 .. _GettingStartedNoneConda:
 
 =====================
-Develop without Conda
+Develop without conda
 =====================
 
 Environment