Removed some text from Express page

Author: CharlieDigital

docs/pages/intermediate/express-vs-minimal-api.md

@@ -2,7 +2,7 @@
 
 Both **Express.js** and **.NET Minimal Web APIs** provide lightweight ways to build web applications, but they differ in performance and built-in features. **Express.js** is a flexible, unopinionated web framework for Node.js, known for its simplicity and middleware-driven architecture. However, since Express relies heavily on JavaScript’s single-threaded event loop, CPU-intensive tasks can become bottlenecks, often requiring worker threads or external services to scale efficiently. Additionally, production-level features like request validation, authentication, and security protections typically require third-party middleware.
 
-**.NET Minimal Web APIs**, introduced in .NET 6, offer a streamlined way to build APIs with high performance and **built-in production-ready features** (no hunting for NPM packages!). Unlike Express, .NET Minimal APIs leverage the highly optimized ASP.NET Core pipeline, benefiting from asynchronous request handling, automatic dependency injection, and built-in middleware for logging, authentication, and rate limiting—many of which only need to be enabled rather than installed separately. Thanks to **Kestrel**, the default web server, Minimal APIs achieve near-native performance with minimal overhead, making them well-suited for high-throughput applications.
+**.NET Minimal Web APIs**, introduced in .NET 6, offer a streamlined way to build APIs with high performance and **built-in production-ready features** (no hunting for NPM packages!). Unlike Express, .NET Minimal APIs leverage the highly optimized ASP.NET Core pipeline, benefiting from asynchronous request handling, automatic dependency injection, and built-in middleware for logging, authentication, and rate limiting—many of which only need to be progressively enabled and configured rather than installed separately.
 
 ## Setting Up