Remove redundant date reference for Docker Model Runner in blog post introduction

Signed-off-by: Lee Calcote <lee.calcote@layer5.io>

Author: leecalcote

src/collections/blog/2025/03-27-docker-model-runner/post.mdx

@@ -20,7 +20,7 @@ import { Link } from "gatsby";
 
 <BlogWrapper>
 
-The shift towards local-first AI development is undeniable, driven by engineers seeking to overcome the practical hurdles of cloud-centric model interaction. Escalating API costs, data privacy concerns when handling sensitive information, network latency impacting iteration speed, and the desire for finer-grained control over execution environments have all highlighted the need for robust local solutions. Docker Model Runner, emerging around April 2025, is Docker's response to these engineering challenges, aiming to significantly streamline how we develop and test AI models locally.  
+The shift towards local-first AI development is undeniable, driven by engineers seeking to overcome the practical hurdles of cloud-centric model interaction. Escalating API costs, data privacy concerns when handling sensitive information, network latency impacting iteration speed, and the desire for finer-grained control over execution environments have all highlighted the need for robust local solutions. Docker Model Runner is Docker's response to these engineering challenges, aiming to significantly streamline how we develop and test AI models locally.  
 
 This post, the first in a series, will dissect Docker Model Runner from an engineering perspective. We'll explore its core technical value propositions and how you can leverage this new toolkit to enhance your AI development workflows.