Apply suggestions from code review

Co-authored-by: bhosmer-ant <[email protected]>

Author: kurtisvg

docs/specification/draft/basic/lifecycle.mdx

@@ -142,9 +142,11 @@ If using HTTP, the client **MUST** include the `MCP-Protocol-Version:
 <protocol-version>` HTTP header during any subsequent requests to the MCP
 server, allowing the MCP server to respond based on the MCP protocol version. 
 
+The protocol version sent by the client **SHOULD** be the one negotiated during [initialization](https://modelcontextprotocol.io/specification/draft/basic/lifecycle#initialization).
+
 If the server receives a request with a missing, invalid, or unsupported
 MCP-Protocol-VERSION, it **MUST** respond with `400 Bad Request`.
-
+For example: `MCP-Protocol-Version: 2024-11-05`
 #### Capability Negotiation
 
 Client and server capabilities establish which optional protocol features will be