docs: remove excessive emojis from native vs guest bindings guide

Cleaned up the documentation to maintain a professional tone by removing
check marks and X marks from capability lists and section headers.

The content remains the same but is now more suitable for technical
documentation while maintaining readability and clarity.

Author: avrabe

docs-site/src/content/docs/guides/host-vs-wasm-bindings.mdx

@@ -75,7 +75,7 @@ Our binding system creates:
 
 Use `{name}_bindings_host` for:
 
-### ✅ Test Applications
+### Test Applications
 ```python
 rust_test(
     name = "component_integration_test", 
@@ -84,7 +84,7 @@ rust_test(
 )
 ```
 
-### ✅ Benchmarking Tools
+### Benchmarking Tools
 ```python
 rust_binary(
     name = "component_benchmark",
@@ -93,7 +93,7 @@ rust_binary(
 )
 ```
 
-### ✅ Development Utilities
+### Development Utilities
 ```python
 rust_binary(
     name = "schema_validator",
@@ -102,7 +102,7 @@ rust_binary(
 )
 ```
 
-### ✅ Mock Implementations
+### Mock Implementations
 ```rust
 // In your test file - runs natively, not in WebAssembly
 use calculator_bindings_host::exports::calculator::math::Guest;
@@ -119,7 +119,7 @@ impl Guest for MockCalculator {
 
 Use `{name}_bindings` for:
 
-### ✅ Guest Component Implementations
+### Guest Component Implementations
 ```rust
 // Guest component source code (src/lib.rs) - compiles to WebAssembly
 use calculator_bindings::exports::calculator::math::Guest;
@@ -148,35 +148,35 @@ rust_wasm_component_bindgen(
 
 ### Native Platform Bindings Can Do
 
-- ✅ **Run natively** on your development machine
-- ✅ **Access component interfaces** and type definitions  
-- ✅ **Import and use** WIT-generated traits and types
-- ✅ **Create mock implementations** for testing
-- ✅ **Build development tools** that understand component interfaces
-- ✅ **Serialize/deserialize** component data types
+- **Run natively** on your development machine
+- **Access component interfaces** and type definitions  
+- **Import and use** WIT-generated traits and types
+- **Create mock implementations** for testing
+- **Build development tools** that understand component interfaces
+- **Serialize/deserialize** component data types
 
 ### Native Platform Bindings Cannot Do
 
-- ❌ **Run as WebAssembly components** in host runtimes like wasmtime
-- ❌ **Export component functions** to other languages via WebAssembly
-- ❌ **Participate in WAC compositions** or component graphs
-- ❌ **Use WASI Preview 2** or component model features
-- ❌ **Be executed by host runtimes** as guest components
+- **Run as WebAssembly components** in host runtimes like wasmtime
+- **Export component functions** to other languages via WebAssembly
+- **Participate in WAC compositions** or component graphs
+- **Use WASI Preview 2** or component model features
+- **Be executed by host runtimes** as guest components
 
 ### Guest Component Bindings Can Do
 
-- ✅ **Run in host runtimes** (wasmtime, browsers, etc.)
-- ✅ **Export component functions** to any language via WebAssembly
-- ✅ **Participate in component compositions** via WAC
-- ✅ **Use WASI Preview 2** filesystem, networking, etc.
-- ✅ **Be distributed** via OCI registries  
-- ✅ **Provide secure sandboxing** and portability
+- **Run in host runtimes** (wasmtime, browsers, etc.)
+- **Export component functions** to any language via WebAssembly
+- **Participate in component compositions** via WAC
+- **Use WASI Preview 2** filesystem, networking, etc.
+- **Be distributed** via OCI registries  
+- **Provide secure sandboxing** and portability
 
 ### Guest Component Bindings Cannot Do
 
-- ❌ **Run natively** on native platforms
-- ❌ **Be used directly** in native applications
-- ❌ **Access native system resources** outside WASI sandbox
+- **Run natively** on native platforms
+- **Be used directly** in native applications
+- **Access native system resources** outside WASI sandbox
 
 ## Common Error and Solution