fix changelog and contributing guide typos

CHANGELOG.md

@@ -11,13 +11,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Added cargo feature `wizard`, enabled by default.
 - Added one cargo feature per backend feature:
-  - `account` including `account-configure`, `account-list`, `account-sync` and the `account` subcommand
-  - `folder` including `folder-add`, `folder-list`, `folder-expunge`, `folder-purge`, `folder-delete` and the `folder` subcommand
-  - `envelope` including `envelope-list`, `envelope-watch`, `envelope-get` and the `envelope` subcommand
-  - `flag` including `flag-add`, `flag-set`, `flag-remove` and the `flag` subcommand
-  - `message` including `message-read`, `message-write`, `message-mailto`, `message-reply`, `message-forward`, `message-copy`, `message-move`, `message-delete`, `message-save`, `message-send` and the `message` subcommand
-  - `attachment` including `attachment-download` and the `attachment` subcommand
-  - `template` including `template-write`, `template-reply`, `template-forward`, `template-save`, `template-send` and the `template` subcommand
+  - `account` including `account-configure`, `account-list`, `account-sync` and the `account-subcmd`
+  - `folder` including `folder-add`, `folder-list`, `folder-expunge`, `folder-purge`, `folder-delete` and the `folder-subcmd`
+  - `envelope` including `envelope-list`, `envelope-watch`, `envelope-get` and the `envelope-subcmd`
+  - `flag` including `flag-add`, `flag-set`, `flag-remove` and the `flag-subcmd`
+  - `message` including `message-read`, `message-write`, `message-mailto`, `message-reply`, `message-forward`, `message-copy`, `message-move`, `message-delete`, `message-save`, `message-send` and the `message-subcmd`
+  - `attachment` including `attachment-download` and the `attachment-subcmd`
+  - `template` including `template-write`, `template-reply`, `template-forward`, `template-save`, `template-send` and the `template-subcmd`
 - Added wizard capability to autodetect IMAP and SMTP configurations, based on the [Thunderbird Autoconfiguration](https://wiki.mozilla.org/Thunderbird:Autoconfiguration) standard.
 - Added back Notmuch backend features.
 
@@ -316,9 +316,9 @@ Few major concepts changed:
 
   The source code has been split into subrepositories:
 
-  - The email logic has been extracted from the CLI and placed in a lib on [sourcehut](https://git.sr.ht/~soywod/himalaya-lib)	
-  - The vim plugin is now in a dedicated repository on [sourcehut](https://git.sr.ht/~soywod/himalaya-vim) as well
-  - This repository only contains the CLI source code (it was not possible to move it to sourcehut because of cross platform builds)
+  - The email logic has been extracted from the CLI and placed in a lib on [SourceHut](https://git.sr.ht/~soywod/himalaya-lib)	
+  - The vim plugin is now in a dedicated repository on [SourceHut](https://git.sr.ht/~soywod/himalaya-vim) as well
+  - This repository only contains the CLI source code (it was not possible to move it to SourceHut because of cross platform builds)
 
 - [**BREAKING**] Renamed `-m|--mailbox` to `-f|--folder`
 

CONTRIBUTING.md

@@ -19,13 +19,13 @@ $ cargo run --feature pgp-gpg -- envelope list
 
 ## Contributing
 
-Himalaya CLI supports open-source, hence the choice of using [sourcehut](https://sourcehut.org/) for managing the project. The only reason why the source code is hosted on GitHub is to build releases for all major platforms (using GitHub Actions). Don't worry, contributing on sourcehut is not a big deal: you just need to send emails! You don't need to create any account. Here a small comparison guide with GitHub:
+Himalaya CLI supports open-source, hence the choice of using [SourceHut](https://sourcehut.org/) for managing the project. The only reason why the source code is hosted on GitHub is to build releases for all major platforms (using GitHub Actions). Don't worry, contributing on SourceHut is not a big deal: you just need to send emails! You don't need to create any account. Here a small comparison guide with GitHub:
 
 The equivalent of **GitHub Discussions** are:
 
 - The [Matrix](https://matrix.org/) chat room [#pimalaya.himalaya](https://matrix.to/#/#pimalaya.himalaya:matrix.org)
-- The sourcehut mailing list. You can consult existing messages [here](https://lists.sr.ht/~soywod/pimalaya). You can "open a new discussion" by sending an email at [~soywod/[email protected]](mailto:~soywod/[email protected]). You can also [subscribe](mailto:~soywod/[email protected]) and [unsubscribe](mailto:~soywod/[email protected]) to the mailing list, so you can receive a copy of all discussions.
+- The SourceHut mailing list. You can consult existing messages [here](https://lists.sr.ht/~soywod/pimalaya). You can "open a new discussion" by sending an email at [~soywod/[email protected]](mailto:~soywod/[email protected]). You can also [subscribe](mailto:~soywod/[email protected]) and [unsubscribe](mailto:~soywod/[email protected]) to the mailing list, so you can receive a copy of all discussions.
 
-The equivalent of **GitHub Issues** is the sourcehut bug tracker. You can consult existing bugs [here](https://todo.sr.ht/~soywod/pimalaya), and you can "open a new issue" by sending an email at [~soywod/[email protected]](mailto:~soywod/[email protected]).
+The equivalent of **GitHub Issues** is the SourceHut bug tracker. You can consult existing bugs [here](https://todo.sr.ht/~soywod/pimalaya), and you can "open a new issue" by sending an email at [~soywod/[email protected]](mailto:~soywod/[email protected]).
 
-The equivalent of **GitHub Pull requests** is the sourcehut mailing list. You can "open a new pull request" by sending an email containing a git patch at [~soywod/[email protected]](mailto:~soywod/[email protected]). The simplest way to send a patch is to use [git send-email](https://git-scm.com/docs/git-send-email), follow [this guide](https://git-send-email.io/) to configure git properly.
+The equivalent of **GitHub Pull requests** is the SourceHut mailing list. You can "open a new pull request" by sending an email containing a git patch at [~soywod/[email protected]](mailto:~soywod/[email protected]). The simplest way to send a patch is to use [git send-email](https://git-scm.com/docs/git-send-email), follow [this guide](https://git-send-email.io/) to configure git properly.