Minor fix

Author: soareschen

content/blog/2026-02-01-v0.6.1-release.md

@@ -97,8 +97,6 @@ As your CGP applications grow in complexity, so does the challenge of verifying
 
 When you compose multiple providers together and something goes wrong, the compiler error messages can be cryptic. The error might point to a deep dependency in the chain, but it won't clearly tell you which individual provider in the composition is actually failing. This forces developers to compile and test repeatedly, changing providers and wiring patterns to narrow down the issue.
 
-Imagine you have a complex provider like `ScaledArea` that calculates the scaled area of a shape, which internally uses another provider `RectangleArea` to calculate the base area. If something breaks, is the problem in `ScaledArea` itself, or in its dependency on `RectangleArea`? Without good tooling, you have to guess and check.
-
 ### Direct Provider Checks with `#[check_providers]`
 
 CGP v0.6.1 introduces the `#[check_providers]` attribute for the `check_components!` macro, which lets you verify that specific providers work correctly with a given context. This is a powerful debugging tool that allows you to isolate and test individual providers before wiring them into your context.
@@ -219,7 +217,7 @@ check_components! {
 }
 ```
 
-The first check verifies that the wired provider works with the context. The second check verifies each individual provider (or provider combination) that makes up your composition. If something is broken, the error messages from these targeted checks will clearly point you to the problematic provider, rather than the entire composition.
+The first check verifies that the wired provider works with the context. The second check verifies each individual provider (or provider combination) that makes up your composition. If something is broken, such as the `width` field is missing, the error messages from these targeted checks will clearly point you to the problematic provider, rather than the entire composition.
 
 This is a game-changer for debugging complex CGP setups. Instead of staring at a wall of compiler errors and trying to trace through the dependency chain, you can surgically test each part of your provider composition.