address minor comments

Signed-off-by: NitishKumar06 <justnitish06@gmail.com>

content/en/blog/2023/sig-release-spotlight/sig-release-spotlight.md

@@ -53,11 +53,11 @@ features in an experimental state, to gather feedback from the community, follow
 couple of Beta releases, where features are more stable and the focus is on fixing bugs. Feedback 
 from users is critical at this stage, to the point where sometimes we need to cut an 
 additional Beta release to address bugs or other concerns that may arise during this phase. Once 
-this is cleared, we cut an Release Candidate (RC) before the actual release. Throughout
+this is cleared, we cut a _release candidate_ (RC) before the actual release. Throughout
 the cycle, efforts are made to update and improve documentation, including release notes 
 and user guides, a process that, in my opinion, deserves its own post.
 
-- **Stabalisation Phase:** A few weeks before the new release, we implement a Code Freeze, and 
+- **Stabilisation Phase:** A few weeks before the new release, we implement a _code freeze_, and 
 no new features are allowed after this point: this allows the focus to shift towards testing 
 and stabalisation. In parallel to the main release, we keep cutting monthly patches of old, 
 officially supported versions of Kubernetes, so you could say that the lifecycle of a Kubernetes