Update keps/sig-instrumentation/4827-component-statusz/README.md

Co-authored-by: Pranshu Srivastava <[email protected]>

Author: richabanker

keps/sig-instrumentation/4827-component-statusz/README.md

@@ -103,7 +103,7 @@ Originating at Google and embedded by default in many internal servers, z-pages
 
 With statusz, we envision the following advantages
 
-* Consolidated and precise information: Presenting critical build data in a clear, concise format, eliminates the need to dig through logs or configurations to gather this essential information. Z-pages offer a distinct advantage over external monitoring solutions by providing insights from within the server itself. This inherent integration eliminates the need for complex external setups and potential network latency issues
+* Consolidated and precise information: Presenting critical build data in a clear, concise format, eliminates the need to dig through logs or configurations to gather this essential information. Z-pages offer a distinct advantage over external monitoring solutions by providing insights from within the server itself. This inherent integration eliminates the need for complex external setups like manual inspection of logs, configuration files, or running external scripts that may be subject to potential network latency issues
 * Streamlined troubleshooting and debugging:  Immediate access to crucial build information like binary version, Go version and compatibility details enables better understanding of the component's state. We hope this interface makes it easier to identify version mismatches or incompatibilities that might contribute to issues, accelerating troubleshooting and debugging efforts
 
 
@@ -145,7 +145,7 @@ We are proposing to add a new endpoint, /statusz on all core Kubernetes componen
 
 ### Data Format and versioning
 
-Initially, the statusz page will exclusively support a plain text format for responses. We will implement these endpoints using versioned URLs, like /v1/statusz, to ensure future compatibility. This versioning strategy allows us to seamlessly introduce structured data formats (e.g., JSON) in the future, through a distinct endpoint such as /v2/statusz, without disrupting existing implementations.
+Initially, the statusz page will exclusively support a plain text format for responses. We will implement these endpoints using versioned URLs, like /statusz/v1, to ensure future compatibility. This versioning strategy allows us to seamlessly introduce structured data formats (e.g., JSON) in the future, through a distinct endpoint such as /statusz/v2, without disrupting existing implementations.
 
 ### Authz and authn
 
@@ -157,7 +157,7 @@ Access to the endpoint will be limited to members of the `system:monitoring grou
 
 #### Request
 * Method: **GET** 
-* Endpoint: **v1/statusz**
+* Endpoint: **/statusz/v1**
 * Body: empty
 
 #### Response fields
@@ -232,7 +232,7 @@ to implement this enhancement.
 
 #### Deprecation
 
-We plan to use the existing strategy for deprecating the zpage as is used for metrics currently, that is
+We plan to use the existing strategy for deprecating a zpage as is used for metrics deprecation currently, that is,
 
 - Announce deprecation and support policy of the z-page
 - Two versions passed since introducing the functionality that deprecates the z-page (to address version skew)