fix typo in page and video (#134)

Author: philmillman

packages/docs-site/src/content/docs/docs/guides/dynamic-config.mdx

@@ -5,7 +5,7 @@ description: Learn how to manage dynamic and static config items in DMNO in your
 
 If you do any front-end development, you're probably used to the concept of replacing references to env vars with actual values _at build time_ (e.g., [vite](https://vitejs.dev/config/shared-options.html#define), [webpack](https://webpack.js.org/plugins/define-plugin/)). This is useful so that:
 - the client doesn't have to fetch config before using it
-- bundlers can drop unreachable code and dependendencies
+- bundlers can drop unreachable code and dependencies
 
 In most frameworks and build tools, this concept is tightly coupled with something being _**public**_, and is triggered via a special prefix (e.g., `NEXT_PUBLIC_`) but can also be dependent on _where and how_ you access the config, especially now that server-side/hybrid rendering is gaining popularity over the totally static JAMStack sites of the last decade.
 

packages/docs-site/src/pages/index.astro

@@ -11,7 +11,7 @@ import intellisenseImg from '@/assets/docs-images/platform-intellisense-example.
 import leakImg from '@/assets/docs-images/security-demo.png';
 import screenshotImg from '@/assets/blog/screenshot-with-comments.png';
 
-const muxId = "dTb7Y3p00ajAOcSF4x00DZN7lkXGU00i2nfW3puCWVfyos";
+const muxId = "FmBLL2H1yt6cEfqz01QVje7LSlI8DtF9Vn18NRsv5o6E";
 ---
 <LandingPage
   title="DMNO"