diff --git a/packages/ui/src/components/shadcn/stories/Select.stories.tsx b/packages/ui/src/components/shadcn/stories/Select.stories.tsx
index da44645c8b6..3a63c0598fc 100644
--- a/packages/ui/src/components/shadcn/stories/Select.stories.tsx
+++ b/packages/ui/src/components/shadcn/stories/Select.stories.tsx
@@ -51,7 +51,7 @@ export function Default() {
   )
 }
 
-export function withSeperators() {
+export function withSeparators() {
   return (
     <Select>
       <SelectTrigger className="w-[180px]">
diff --git a/studio/components/interfaces/Integrations/ProjectLinker.tsx b/studio/components/interfaces/Integrations/ProjectLinker.tsx
index ac592a45df6..9365d763103 100644
--- a/studio/components/interfaces/Integrations/ProjectLinker.tsx
+++ b/studio/components/interfaces/Integrations/ProjectLinker.tsx
@@ -292,7 +292,7 @@ const ProjectLinker = ({
             loadingForeignProjects ||
             loadingSupabaseProjects ||
             isLoading ||
-            // check wether both project types are not undefined
+            // check whether both project types are not undefined
             !selectedSupabaseProject ||
             !selectedForeignProject
           }
diff --git a/studio/data/__templates/README.md b/studio/data/__templates/README.md
index d3be296edcd..9a5d6f25d6f 100644
--- a/studio/data/__templates/README.md
+++ b/studio/data/__templates/README.md
@@ -72,7 +72,7 @@ return (
 
 ### Mutations
 
-The parameter `onError` can be passed when intializing the mutation, where an appropriate UI behavior should be triggered (usually a toast will be fine). If `onError` is not provided, we will then default to a toast message that will be called from within the mutation itself which should handle most cases. However, if there is a specific way that the error should be handled, then this should be passed via the `onError` parameter. (There's no need to repeat the error handling if the default behavior is sufficient)
+The parameter `onError` can be passed when initializing the mutation, where an appropriate UI behavior should be triggered (usually a toast will be fine). If `onError` is not provided, we will then default to a toast message that will be called from within the mutation itself which should handle most cases. However, if there is a specific way that the error should be handled, then this should be passed via the `onError` parameter. (There's no need to repeat the error handling if the default behavior is sufficient)
 
 We should also aim to convert most of the `mutateAsync` to `mutate`, otherwise we'd need to wrap all the `mutateAsync` calls in try catches just to ensure that the client doesn't crash when the request throws an error in the mutation. There's currently a mix due to the Form component that we're using, in particular when a method from the Form component such as `resetForm` needs to be called after the request is completed successfully.
 
@@ -88,7 +88,7 @@ const { mutate: someAction } = useMutation({
 
 const onConfirm = async () => {
   // Assuming that your mutation needs a URL param like project ref
-  // This check is just to satistfy the linting - there's an implicit assumption that
+  // This check is just to satisfy the linting - there's an implicit assumption that
   // projectRef here will definitely be available since its obtained from the URL
   if (!projectRef) return console.error('Project ref is required')