From 5ab542a8d092edcf72b70580a025cd1196997901 Mon Sep 17 00:00:00 2001 From: Samantaz Fox Date: Sun, 21 Apr 2024 16:58:16 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: absidue <48293849+absidue@users.noreply.github.com> --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 31e776b7..3a29df99 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,7 +19,7 @@ with Invidious. Here is a summary: * [Testing](#testing): You're an advanced user, who is already running their own instance, is not worried of compiling Invidious from source, and wants to help us test bug fixes or new features. -* [Development](#development): You're a developper and want to contribute code, or help with +* [Development](#development): You're a developer and want to contribute code, or help with reviewing the code written by others. @@ -148,7 +148,7 @@ with us on Matrix or IRC. We'll do our best to give you a better understanding o Once you have deployed the patch on your test instance, try the changes mentionned in the pull request. Often times, the linked issue might contain examples of channels/comments/videos impacted. -Definitely use those to check that the behaviot you see is the expected one. After that, add a +Definitely use those to check that the behavior you see is the expected one. After that, add a comment on that PR with your test methodology and your findings. Add screenshots (for interface changes) and code snippets (for API changes) as needed.