diff options
author | Simon Tournier <zimon.toutoune@gmail.com> | 2024-02-02 17:11:30 +0100 |
---|---|---|
committer | Simon Tournier <zimon.toutoune@gmail.com> | 2024-02-02 17:12:38 +0100 |
commit | f2e5e94544fdd16d681046cf80bafa7aa13c1f27 (patch) | |
tree | cff6158dc5b870be8d5c67d0e4aeccfdb36ed437 /doc | |
parent | b88bff628d1eab17a5633f1454c9639a2b946446 (diff) | |
download | guix-f2e5e94544fdd16d681046cf80bafa7aa13c1f27.tar.gz |
doc: contributing: Fix typo.
* doc/contributing.texi (Reviewing the Work of Others): Fix typo. Change-Id: I4d3afd4f7e47dbda8a43fdf7f18c7c233d1c8762
Diffstat (limited to 'doc')
-rw-r--r-- | doc/contributing.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi index a1b9e3586b..9a28a58c86 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -2339,7 +2339,7 @@ Perhaps the biggest action you can do to help GNU Guix grow as a project is to review the work contributed by others. You do not need to be a committer to do so; applying, reading the source, building, linting and running other people's series and sharing your comments about your -experience will give some confidence to committers. Basically, you gmust +experience will give some confidence to committers. Basically, you must ensure the check list found in the @ref{Submitting Patches} section has been correctly followed. A reviewed patch series should give the best chances for the proposed change to be merged faster, so if a change you |