Fix cspell

cli/src/commands/invite/claim.rs

@@ -16,7 +16,8 @@ use crate::utils::*;
 
 #[derive(clap::Parser)]
 pub struct Args {
-    /// Server invitation address (e.g.: parsec3://127.0.0.1:41997/Org?no_ssl=true&a=claim_shamir_recovery&p=xBA2FaaizwKy4qG5cGDFlXaL)
+    // cspell:disable-next-line
+    /// Server invitation address (e.g.: parsec3://127.0.0.1:41997/Org?no_ssl=true&a=claim_shamir_recovery&p=xBA2FaaizwKy4qG5cGDFlXaL`)
     #[arg(short, long)]
     addr: ParsecInvitationAddr,
     /// Read the password from stdin instead of a TTY.

libparsec/crates/types/tests/unit/addr.rs

@@ -489,7 +489,8 @@ fn invitation_addr_bad_type(
                 &url,
                 AddrError::InvalidParamValue {
                     param: "a",
-                    help: "Expected `a=claim_user` or `a=claim_device`".to_string(),
+                    help: "Expected `a=claim_user`, `a=claim_device` or `a=claim_shamir_recovery`"
+                        .to_string(),
                 },
             );
         }

server/parsec/components/memory/invite.py

@@ -544,7 +544,7 @@ async def info_as_invited(
             case InvitationType.SHAMIR_RECOVERY:
                 shamir_recovery_invitation = self._get_shamir_recovery_invitation(org, invitation)
                 if shamir_recovery_invitation is None:
-                    # TODO: The invitation is not actually deleted, but the corresoinding setup has
+                    # TODO: The invitation is not actually deleted, but the corresponding setup has
                     # been deleted. This is a bit misleading, we should find a way to differentiate
                     # between the two cases.
                     return InviteAsInvitedInfoBadOutcome.INVITATION_DELETED