fix: typos in packages/ (#21216)

Found via codespell

Co-authored-by: Udit Takkar <53316345+Udit-takkar@users.noreply.github.com>

packages/features/bookings/Booker/config.ts

@@ -142,7 +142,7 @@ export const getBookerSizeClassNames = (
     // Small calendar defaults
     layout === BookerLayouts.MONTH_VIEW && getBookerMetaClass("[--booker-meta-width:240px]"),
     // Meta column gets wider in booking view to fit the full date on a single row in case
-    // of a multi occurence event. Also makes form less wide, which also looks better.
+    // of a multi occurrence event. Also makes form less wide, which also looks better.
     layout === BookerLayouts.MONTH_VIEW &&
       bookerState === "booking" &&
       `[--booker-main-width:420px] ${getBookerMetaClass("lg:[--booker-meta-width:340px]")}`,

packages/features/bookings/Booker/utils/isTimeslotAvailable.ts

@@ -92,7 +92,7 @@ export const isTimeSlotAvailable = ({
   }
 
   const dateInGMT = isValidISOFormat(slotToCheckInIso) ? slotToCheckInIso.split("T")[0] : null;
-  // If the date is not in ISO format, we could errorneously consider the slot unavailable, so be on the safe side and consider it available
+  // If the date is not in ISO format, we could erroneously consider the slot unavailable, so be on the safe side and consider it available
   // Though this could be a false positive, it's better to consider the slot available than unavailable
   if (!dateInGMT) return true;
 

packages/lib/EventManager.ts

@@ -152,7 +152,8 @@ export default class EventManager {
         (cred) => cred.type.endsWith("_calendar") && !cred.type.includes("other_calendar")
       )
       // see https://github.com/calcom/cal.com/issues/11671#issue-1923600672
-      // This sorting is mostly applicable for fallback which happens when there is no explicity destinationCalendar set. That could be true for really old accounts but not for new
+      // This sorting is mostly applicable for fallback which happens when there is no explicit destinationCalendar set.
+      // That could be true for really old accounts but not for new
       .sort(latestCredentialFirst)
       // Keep Delegation Credentials first so because those credentials never expire and are preferred.
       // Also, those credentials have consistent permission for all the members avoiding the scenario where user doesn't give all permissions

packages/lib/bookings/findQualifiedHostsWithDelegationCredentials.ts

@@ -145,7 +145,7 @@ export const findQualifiedHostsWithDelegationCredentials = async <
     };
   }
 
-  //if segement matching doesn't return any hosts we fall back to all round robin hosts
+  //if segment matching doesn't return any hosts we fall back to all round robin hosts
   const officalRRHosts = hostsAfterSegmentMatching.length ? hostsAfterSegmentMatching : roundRobinHosts;
 
   const hostsAfterContactOwnerMatching = applyFilterWithFallback(

packages/lib/delegationCredential/server.ts

@@ -577,7 +577,7 @@ export async function getCredentialForCalendarCache({ credentialId }: { credenti
     if (!delegationCredential) {
       credentialForCalendarService = null;
     } else {
-      // We preparare a credential that is in-db(in constrast with an in-memory credential used elsewhere where we generate CredentialForCalendarService)
+      // We prepare a credential that is in-db(in contrast with an in-memory credential used elsewhere where we generate CredentialForCalendarService)
       credentialForCalendarService = {
         ...delegationCredential,
         id: credential.id,

packages/ui/components/navigation/tabs/navigation.test.tsx

@@ -97,7 +97,7 @@ describe("Navigation Components", () => {
         href: "https://external.com",
         isExternalLink: true,
         icon: "external",
-        "data-testid": "Exteral",
+        "data-testid": "External",
       },
       {
         name: "Disabled",