fix typos in blog

apps/formbricks-com/components/shared/FeedbackButton.tsx

@@ -20,16 +20,16 @@ export default function FeedbackButton() {
       />
       <Script id="feedback-setup">{`
       window.formbricks = {
-      config: {
-        hqUrl: "https://xm.formbricks.com",
-        formId: "clchup08o0000lj08526vdujt",
-        contact: {
-          name: "Matti",
-          position: "Co-Founder",
-          imgUrl: "https://avatars.githubusercontent.com/u/675065?s=128&v=4",
+        ...window.formbricks,
+        config: {
+          hqUrl: "https://xm.formbricks.com",
+          formId: "clchup08o0000lj08526vdujt",
+          contact: {
+            name: "Matti",
+            position: "Co-Founder",
+            imgUrl: "https://avatars.githubusercontent.com/u/675065?s=128&v=4",
+          },
         },
-      },
-      ...window.formbricks,
     };`}</Script>
       {scriptReady && (
         <button

apps/formbricks-com/pages/blog/weekly-update-060123/index.mdx

@@ -26,7 +26,7 @@ _Happy new year to all of you (and happy birthday to Johannes 🎂). The Feedbac
 - Config for styling Feedback Box pop-up shipped
 - Pipelines added to XM Dashboard
 - PR for [cal.com](http://cal.com) Feedback Box (prototype)
-- Right now: Seperating wrapper from content
+- Right now: Separating wrapper from content
 - Johannes moving to Kiel
 
 ## Styling the Feedback Box via config
@@ -78,7 +78,7 @@ _After all, the modules we built for Formbricks come in handy here and there :)_
 
 ## PR at [Cal.com](https://cal.com) repo for Feedback Box
 
-We’ve embedded the prototype of the feedback box into Cal.com and will open a PR in the coming days to get feedback from the team. We aren’t fully satisfied with the result yet: it still feels like an alien element in the UI. To tackle that, we start working on a task we planned for the next use case: seperating the form content from the wrapper (see next point).
+We’ve embedded the prototype of the feedback box into Cal.com and will open a PR in the coming days to get feedback from the team. We aren’t fully satisfied with the result yet: it still feels like an alien element in the UI. To tackle that, we start working on a task we planned for the next use case: separating the form content from the wrapper (see next point).
 
 <Image src={CalcomPreview} alt="Calcom Preview" className="rounded-lg" />
 
@@ -90,7 +90,7 @@ We have to do more tweaking to get to a result which is
 - easily adaptable to any look & feel
 - maintainable
 
-To achieve this, we have to do quite a bit of the groundwork we hoped to postpone until we build out the next best practice: The Superhuman PMF survey. We’ll now seperate the content from the wrapper to gain flexibility. Many SaaS products have a standard wrapper we want to be able to easily use for a consistent look & feel.
+To achieve this, we have to do quite a bit of the groundwork we hoped to postpone until we build out the next best practice: The Superhuman PMF survey. We’ll now separate the content from the wrapper to gain flexibility. Many SaaS products have a standard wrapper we want to be able to easily use for a consistent look & feel.
 
 ## Moving to Kiel