🔄 synced file(s) with conda/infrastructure (#34)

Co-authored-by: Conda Bot <conda-bot@users.noreply.github.com>
conda · Aug 29, 2023 · e957a23 · e957a23
1 parent 766a5eb
commit e957a23
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml
@@ -27,7 +27,7 @@ jobs:
           # (default: secrets.GITHUB_TOKEN)
           token: ${{ secrets.CLA_ACTION_TOKEN }}
           # [required]
-          # Label to apply to contributor's PR once CLA is singed
+          # Label to apply to contributor's PR once CLA is signed
           label: cla-signed
 
           # [required]

diff --git a/HOW_WE_USE_GITHUB.md b/HOW_WE_USE_GITHUB.md
@@ -272,7 +272,7 @@ please post details to the [Nucleus forums](https://community.anaconda.cloud/).
 <pre>
 Hi [@username],
 
-Thanks for voicing your concern about the performance of our dependency solver. To fix this, our official recommendation is using the "conda-libmamba-solver" instead of the default "classic" solver (more information about the "conda-libmamba-solver" can be found here: https://conda.github.io/conda-libmamba-solver/getting-started/).
+Thanks for voicing your concern about the performance of the classic dependency solver. To fix this, our official recommendation is using the new default "conda-libmamba-solver" instead of the classic solver (more information about the "conda-libmamba-solver" can be found here: https://conda.github.io/conda-libmamba-solver/getting-started/).
 
 In most cases "conda-libmamba-solver" should be significantly faster than the "classic" solver. We hope it provides you with a much better experience going forward.
 </pre>