aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Hedy Li <[email protected]>2021-10-18 09:26:29 +0800
committerGravatar Hedy Li <[email protected]>2021-10-18 09:26:29 +0800
commit01db2676c43994755ab18b7609943dae8982c822 (patch)
treeda0ecdfed5441290b73516edd9fae7212d3150b8
parentFix typo 'fied' in apps/api/tests/test_offensive_message.py (diff)
Fix typos in contributing guides
- succint -> succinct - seperated -> separated
-rw-r--r--pydis_site/apps/content/resources/guides/pydis-guides/contributing/sir-lancebot/env-var-reference.md4
-rw-r--r--pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/cli.md2
-rw-r--r--pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/pycharm.md2
3 files changed, 4 insertions, 4 deletions
diff --git a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/sir-lancebot/env-var-reference.md b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/sir-lancebot/env-var-reference.md
index 9ad014a2..51587aac 100644
--- a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/sir-lancebot/env-var-reference.md
+++ b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/sir-lancebot/env-var-reference.md
@@ -61,10 +61,10 @@ These variables might come in handy while working on certain cogs:
| Cog | Environment Variable | Description |
| -------- | -------- | -------- |
-| Advent of Code | `AOC_LEADERBOARDS` | List of leaderboards seperated by `::`. Each entry should have an `id,session cookie,join code` seperated by commas in that order. |
+| Advent of Code | `AOC_LEADERBOARDS` | List of leaderboards separated by `::`. Each entry should have an `id,session cookie,join code` separated by commas in that order. |
| Advent of Code | `AOC_STAFF_LEADERBOARD_ID` | Integer ID of the staff leaderboard. |
| Advent of Code | `AOC_ROLE_ID` | ID of the advent of code role.
-| Advent of Code | `AOC_IGNORED_DAYS` | Comma seperated list of days to ignore while calculating score. |
+| Advent of Code | `AOC_IGNORED_DAYS` | Comma separated list of days to ignore while calculating score. |
| Advent of Code | `AOC_YEAR` | Debug variable to change the year used for AoC. |
| Advent of Code | `AOC_CHANNEL_ID` | The ID of the #advent-of-code channel |
| Advent of Code | `AOC_COMMANDS_CHANNEL_ID` | The ID of the #advent-of-code-commands channel |
diff --git a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/cli.md b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/cli.md
index 5f196837..94f94d57 100644
--- a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/cli.md
+++ b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/cli.md
@@ -27,7 +27,7 @@ If you use SSH, use `[email protected]:python-discord/sir-lancebot.git` for the ups
You will be committing your changes to a new branch rather than to `main`.
Using branches allows you to work on muiltiple pull requests without conflicts.
-You can name your branch whatever you want, but it's recommended to name it something succint and relevant to the changes you will be making.
+You can name your branch whatever you want, but it's recommended to name it something succinct and relevant to the changes you will be making.
Run the following commands to create a new branch. Replace `branch_name` with the name you wish to give your branch.
```sh
diff --git a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/pycharm.md b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/pycharm.md
index 3f7fefa0..e0b2e33c 100644
--- a/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/pycharm.md
+++ b/pydis_site/apps/content/resources/guides/pydis-guides/contributing/working-with-git/pycharm.md
@@ -27,7 +27,7 @@ The following will use the [Sir-Lancebot](https://github.com/python-discord/sir-
## Creating a New Branch
> You will be committing your changes to a new branch rather than to `main`. Using branches allows you to work on multiple pull requests at the same time without conflicts.
-> You can name your branch whatever you want, but it's recommended to name it something succint and relevant to the changes you will be making.
+> You can name your branch whatever you want, but it's recommended to name it something succinct and relevant to the changes you will be making.
> Before making new branches, be sure to checkout the `main` branch and ensure it's up to date.