more review comments

Author: findleyr

internal/docs/client.src.md

@@ -27,7 +27,7 @@ method. To receive notifications about root changes, set
 ## Sampling
 
 [Sampling](https://modelcontextprotocol.io/specification/2025-06-18/client/sampling)
-is a way for server's to leverage the client's AI capabilities. It is
+is a way for servers to leverage the client's AI capabilities. It is
 implemented in the SDK as follows:
 
 **Client-side**: To add the `sampling` capability to a client, set 
@@ -49,7 +49,7 @@ allows servers to request user inputs. It is implemented in the SDK as follows:
 The elicitation handler must return a result that matches the requested schema;
 otherwise, elicitation returns an error.
 
-**Server-side**: To use eliciation from the server, call
+**Server-side**: To use elicitation from the server, call
 [`ServerSession.Elicit`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#ServerSession.Elicit).
 
 %include ../../mcp/client_example_test.go elicitation -

internal/docs/protocol.src.md

@@ -24,7 +24,7 @@ session.
   [`ClientSession`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#ClientSession).
   This session is initialized during the `Connect` method, and provides methods
   to communicate with the server peer.
-- A `Server` is a logical MCP server, configure with various
+- A `Server` is a logical MCP server, configured with various
   [`ServerOptions`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#ServerOptions).
 - When a server is connected to a client using
   [`Server.Connect`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#Server.Connect),
@@ -70,7 +70,7 @@ newline-delimited JSON over its stdin/stdout.
 
 **Client-side**: the client side of the `stdio` transport is implemented by
 [`CommandTransport`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#CommandTransport),
-which starts the a given `exec.Cmd` as a subprocess and communicates over its
+which starts the a `exec.Cmd` as a subprocess and communicates over its
 stdin/stdout.
 
 **Server-side**: the server side of the `stdio` transport is implemented by

mcp/client_example_test.go

@@ -62,7 +62,7 @@ func Example_roots() {
 func Example_sampling() {
 	ctx := context.Background()
 
-	// Create a client with a single root.
+	// Create a client with a sampling handler.
 	c := mcp.NewClient(&mcp.Implementation{Name: "client", Version: "v0.0.1"}, &mcp.ClientOptions{
 		CreateMessageHandler: func(_ context.Context, req *mcp.CreateMessageRequest) (*mcp.CreateMessageResult, error) {
 			return &mcp.CreateMessageResult{
@@ -102,7 +102,7 @@ func Example_elicitation() {
 	ctx := context.Background()
 	ct, st := mcp.NewInMemoryTransports()
 
-	s := mcp.NewServer(testImpl, nil)
+	s := mcp.NewServer(&mcp.Implementation{Name: "server", Version: "v0.0.1"}, nil)
 	ss, err := s.Connect(ctx, st, nil)
 	if err != nil {
 		log.Fatal(err)

mcp/mcp_example_test.go

@@ -16,7 +16,7 @@ import (
 
 // !+lifecycle
 
-func Example_lifeCycle() {
+func Example_lifecycle() {
 	ctx := context.Background()
 
 	// Create a client and server.

mcp/streamable_example_test.go

@@ -19,7 +19,7 @@ import (
 // !+streamablehandler
 
 func ExampleStreamableHTTPHandler() {
-	// Create a new stramable handler, using the same MCP server for every request.
+	// Create a new streamable handler, using the same MCP server for every request.
 	//
 	// Here, we configure it to serves application/json responses rather than
 	// text/event-stream, just so the output below doesn't use random event ids.