fix: Remove the redundant "See Also" section from the document to simplify the content

Author: TBXark

content/docs/components/_index.md

@@ -14,4 +14,3 @@ Explore Sphere's building blocks and repositories.
   {{< card link="protoc-gen-sphere-binding" title="protoc-gen-sphere-binding" icon="document-duplicate" >}}
   {{< card link="protoc-gen-sphere-errors" title="protoc-gen-sphere-errors" icon="variable" >}}
 {{< /cards >}}
-

content/docs/components/protoc-gen-route.md

@@ -394,8 +394,3 @@ service UserService {
 - Use with `protoc-gen-sphere` for HTTP routing
 - Combine with `protoc-gen-sphere-errors` for consistent error handling
 - Works with any transport layer that can use the generated interfaces
-
-## See Also
-
-- Concepts: ../../concepts/protocol-and-codegen
-- Component: ./protoc-gen-sphere

content/docs/components/protoc-gen-sphere-binding.md

@@ -277,9 +277,3 @@ func inspectTags() {
     }
 }
 ```
-
-## See Also
-
-- Guides: ../../guides/api-definitions
-- Component: ./protoc-gen-sphere
-- Concepts: ../../concepts/protocol-and-codegen

content/docs/components/protoc-gen-sphere-errors.md

@@ -199,8 +199,3 @@ When used with Sphere's HTTP server utilities, these errors are automatically co
 - Sphere's Gin layer maps these to structured JSON with correct HTTP status
 - Pair with a global error parser if you need to merge validation/notfound/custom errors
 - The generated errors integrate seamlessly with Sphere's server utilities for consistent API responses
-
-## See Also
-
-- Guides: ../../guides/error-handling
-- Concepts: ../../concepts/protocol-and-codegen

content/docs/components/protoc-gen-sphere.md

@@ -45,10 +45,3 @@ plugins:
 Notes
 - Works hand-in-hand with Sphere’s Gin helpers: `WithJson`, `ShouldBindJSON`, `ShouldBindUri`, `ShouldBindQuery`
 - Pair with `protoc-gen-sphere-binding` to inject binding tags into generated structs
-
-## See Also
-
-- Guides: ../../guides/api-definitions
-- Component: ./protoc-gen-sphere-binding
-- Component: ./protoc-gen-sphere-errors
-- Concepts: ../../concepts/protocol-and-codegen

content/docs/components/sphere-cli.md

@@ -173,10 +173,4 @@ If generated code seems out of sync:
 ```shell
 make clean    # Clean generated files
 make gen/all  # Regenerate everything
-```
-
-## See Also
-
-- [Quick Start](../../getting-started/quickstart) - Complete project setup guide
-- [Project Structure](../../concepts/project-structure) - Understanding the generated project layout
-- [Components Overview](../) - Details about protoc plugins used by sphere-cli
+```

content/docs/concepts/proto-packages.md

@@ -48,12 +48,3 @@ Purpose
 Use when
 - You build adapters beyond HTTP or need custom routing hints
 
-See also
-- Component using options: ../components/protoc-gen-route
-
-## See Also
-
-- API Definitions Guide: ../guides/api-definitions
-- Error Handling Guide: ../guides/error-handling
-- Component: ../components/protoc-gen-route
-

content/docs/concepts/protocol-and-codegen.md

@@ -34,18 +34,6 @@ Your `.proto` files serve as the authoritative definition of:
 - **HTTP mapping** (via annotations)
 - **Field constraints** (via validation rules)
 
-### Service Definitions
-
-Services declare operations and HTTP mappings via annotations. See ../guides/api-definitions for end‑to‑end examples.
-
-### Message Definitions
-
-Messages define the request/response contracts. Field binding is controlled with sphere/binding options; examples live in ../guides/api-definitions.
-
-### Error Definitions
-
-Define error enums with HTTP status/reason/message using sphere/errors. Usage and patterns are covered in ../guides/error-handling.
-
 ## Code Generation Pipeline
 
 ### Generator Chain
@@ -166,11 +154,4 @@ proto/
 1. **Comprehensive coverage**: Define errors for all failure modes
 2. **Appropriate status codes**: Use correct HTTP status codes
 3. **Clear messages**: Write user-friendly error messages
-4. **Structured data**: Include relevant context in errors
-
-## See Also
-
-- [API Definitions Guide](../guides/api-definitions) - Detailed HTTP mapping rules and examples
-- [Error Handling Guide](../guides/error-handling) - Comprehensive error patterns and implementation
-- [Components Overview](../components/) - Individual generator documentation and configuration
-- [Project Structure](project-structure) - How generated code fits into the overall project layout
+4. **Structured data**: Include relevant context in errors

content/docs/getting-started/quickstart.md

@@ -172,11 +172,3 @@ make gen/dts
 3. **Business Logic**: Implement service methods in `internal/service/**`
 4. **Wire and Run**: `make gen/wire` → `make run`
 5. **Client SDKs**: `make gen/dts` for TypeScript clients
-
-## Next Steps
-
-- [Project Structure](../concepts/project-structure) - Understand the directory layout
-- [API Definitions](../guides/api-definitions) - Learn HTTP mapping and binding rules  
-- [Error Handling](../guides/error-handling) - Define typed, standardized errors
-- [Development Workflow](workflow) - Complete development process
-

content/docs/getting-started/workflow.md

@@ -83,6 +83,3 @@ make run
 - **Test early**: Use generated Swagger UI to verify endpoints
 - **Iterate fast**: Small changes → quick regeneration cycles
 - **Version APIs**: Use proto package versioning for breaking changes
-
-See [Quick Start](quickstart) for the complete setup process.
-