update pricing (#2022)

marketing/app/pricing/page.tsx

@@ -47,10 +47,11 @@ export default function Pricing() {
       </Head>
       <div className="flex flex-col gap-6 justify-center z-40 py-20 mx-auto">
         <h1 className="text-center text-gray-900 font-semibold text-3xl lg:text-5xl font-satoshi pt-10 bg-white/50">
-          Simple, Transparent Pricing
+          Flexible Pricing
         </h1>
         <div className="text-center text-gray-800 font-semibold text-lg font-satoshi bg-white/50 pt-6">
-          Pricing shouldn&apos;t be complicated, so we made it easy.
+          From Open Source to Enterprise, Neosync has flexible pricing and
+          packaging that can work for every company
         </div>
         <div className="flex flex-col lg:flex-row items-center justify-center gap-6 pt-10">
           <OpenSourcePlan />
@@ -175,9 +176,9 @@ function FreePlan(): ReactElement {
 
 function TeamPlan(): ReactElement {
   const features = [
-    '5M records/mo ($60/1M after)',
+    'Unlimited Records',
     'Unlimited Jobs',
-    '5 users ($10/user after)',
+    'Unlimited Users',
     'US or EU Region',
     'Social, SSO',
     'Neosync Infrastructure',
@@ -197,8 +198,7 @@ function TeamPlan(): ReactElement {
             </Badge>
           </div>
           <div className="flex justify-center flex-row gap-2">
-            <div className="text-3xl ">$299</div>
-            <div className="text-sm self-end pb-1">/mo</div>
+            <div className="text-3xl ">Contact Us</div>
           </div>
         </div>
         <Separator className="mt-6" />
@@ -244,7 +244,7 @@ function CustomPlan(): ReactElement {
   ];
 
   return (
-    <div className="border-2 border-gray-400 rounded-xl p-8 lg:mt-28 lg:w-[300px] bg-gradient-to-b from-[#ffffff] to-[#f3f3f3]">
+    <div className="border-2 border-gray-400 rounded-xl p-8 lg:mt-28 lg:w-[310px] bg-gradient-to-b from-[#ffffff] to-[#f3f3f3]">
       <div className="flex flex-col gap-6">
         <div className="flex justify-center">
           <Badge variant="outline" className="border-gray-400 border">

marketing/content/blog/3-types-of-deployments.mdx

@@ -14,7 +14,7 @@ import InlineBlogCode from '../../components/codeblocks/InlineBlogCode.tsx';
 
 One of the main benefits of using a container orchestration system like Kubernetes is that you have a lot of control over your deployment strategy and how you deploy software. In a traditional software environment, deployments or upgrades to applications result in downtime and disruption of service which can frustrate users. In today's cloud native world, users expect that software should be available at all times and in all time zones.
 
-Now, thanks to continuous integration and continuous deployment (CI/CD) — a key component of [DevOps methodology](https://www.nucleuscloud.com/blog/sre-devops-platformeng) — deployments aren’t limited to a monthly or quarterly basis. Additionally, with the rise of [platform engineering](https://www.nucleuscloud.com/blog/what-is-platform-engineering), which is further accelerating the speed at which developers can build and deploy new or improved features, deployments are happening all of the time.
+Now, thanks to continuous integration and continuous deployment (CI/CD) — a key component of DevOps methodology — deployments aren’t limited to a monthly or quarterly basis. Additionally, with the rise of [platform engineering](/blog/what-is-platform-engineering), which is further accelerating the speed at which developers can build and deploy new or improved features, deployments are happening all of the time.
 
 In this blog, we'll walk through three deployment strategies that you can implement to avoid down-time when deploying your software.
 
@@ -34,7 +34,7 @@ Lets take a look at all three of these zero-downtime deployment approaches in mo
 
 ![rolling](https://assets.nucleuscloud.com/neosync/blog/rollingdeploy.png)
 
-A rolling deployment is the default deployment strategy used in Kubernetes. It updates pods one by one by replacing the existing version of a pod with the new version, without cluster downtime. The update uses a [readiness probe](https://www.nucleuscloud.com/blog/health-checks) to check if the new pod is ready before scaling down the old pods.
+A rolling deployment is the default deployment strategy used in Kubernetes. It updates pods one by one by replacing the existing version of a pod with the new version, without cluster downtime. The update uses a readiness probe to check if the new pod is ready before scaling down the old pods.
 
 Let's look at this process in more detail with an example.
 

marketing/content/blog/introducing-custom-transformers.mdx

@@ -10,7 +10,7 @@ authors:
 
 ## Introduction
 
-Developers love flexibility. They want to be able to do things their own way and transforming data is no different. Today I'm excited to give developers that flexibility in [Neosync](https://githunb.com/nucleuscloud/neosync) with Custom Code Transformers.
+Developers love flexibility. They want to be able to do things their own way and transforming data is no different. Today I'm excited to give developers that flexibility in [Neosync](https://github.com/nucleuscloud/neosync) with Custom Code Transformers.
 
 ## What is a Transformer?