docs: refine docs

Author: zxch3n

pages/docs/concepts/attached_detached.mdx

@@ -45,14 +45,15 @@ doc.getText("text").insert(2, " -> v2");
 doc.checkout(v1);
 console.log(doc.isDetached()); // true
 console.log(doc.getText("text").toString()); // "v1"
+```
 
 
 ## Container States
 
 ### Detached (Standalone)
 - Created with constructors (`new LoroMap()`)
 - Not part of any document
-- No ContainerID
+- No valid ContainerID
 - Used as templates
 
 ```ts twoslash
@@ -87,7 +88,7 @@ console.log(attached.isAttached()); // true - new attached copy
 | **Purpose** | Version control | Document membership |
 | **When** | Time travel, branching | Adding to document |
 | **Independence** | N/A | Independent from doc state |
-| **Editing** | Restricted when detached | Always allowed if attached |
+| **Editing** | Restricted when detached | Always allowed |
 
 ## Common Use Cases
 
@@ -116,15 +117,8 @@ list.insertContainer(0, template);
 list.insertContainer(1, template);
 ```
 
-## Best Practices
-
-- **Check before editing**: `if (doc.isDetached()) doc.attach()`
-- **Use templates**: Keep containers detached for reuse
-- **Remember attachment is one-way**: Original stays detached
-- **Re-attach after time travel**: Don't forget to return to latest
-
 ## Related Documentation
 
 - [OpLog and DocState](./oplog_docstate) - Understanding version states
 - [Containers](./container) - Container types and usage
-- [Time Travel](../user-guide/time-travel) - Using checkout and branching
+- [Time Travel](../user-guide/time-travel) - Using checkout and branching

pages/docs/concepts/cursor_stable_positions.mdx

@@ -7,11 +7,11 @@ description: "Understanding cursor and stable position systems in Loro for maint
 
 ## Quick Reference
 
-**Cursors** maintain stable positions across concurrent edits by anchoring to operation IDs instead of indices. Essential for collaborative editing features like shared cursors and persistent annotations.
+**Cursors** maintain stable positions across concurrent edits by anchoring to operation IDs instead of indices. Essential for collaborative editing features like collaborative cursors and persistent annotations.
 
 ## How It Works
 
-Cursors anchor to operation IDs, not indices:
+Cursors anchor to operation IDs and ContainerIDs, not indices:
 
 ```
 Text:    H e l l o   W o r l d
@@ -40,9 +40,10 @@ text.insert(0, "ABC");
 const cursor = text.getCursor(1, -1); // Before 'B'
 text.insert(1, "X"); // Insert at cursor
 // Result: "AXBC", cursor still before 'B'
+const pos = text.getCursorPos(cursor);
+console.log(pos); // { offset: 2, side: Side.Before }
 ```
 
-
 ## Common Use Cases
 
 ### Text Selections
@@ -66,15 +67,14 @@ const doc = new LoroDoc();
 const list = doc.getList("items");
 list.insert(0, ["a", "b", "c"]);
 
-const cursor = list.getCursor(1, 0); // After "a"
+const cursor = list.getCursor(0, 1); // After "a"
 list.insert(0, "new"); // Cursor adjusts automatically
 ```
 
 ## Code Example
 
 ```ts twoslash
 import { LoroDoc, LoroText, Cursor } from "loro-crdt";
-// ---cut---
 class CollaborativeSelection {
   private anchor!: Cursor;
   private head!: Cursor;
@@ -105,15 +105,8 @@ class CollaborativeSelection {
 }
 ```
 
-## Best Practices
-
-- **Side parameters**: Use -1 for starts, 1 for ends, 0 for simple positions
-- **Handle updates**: Check for and persist cursor updates
-- **Account for deletions**: Check `position.side` for deleted content
-- **UTF-16 awareness**: Emoji and special chars use multiple indices
-
 ## Related Documentation
 
 - [Text Container](../containers/text) - Text editing with cursors
 - [Collaborative Editing](../user-guide/collaborative-editing) - Building editors
-- [Events](../user-guide/events) - Cursor change events
+- [Events](../user-guide/events) - Cursor change events

pages/docs/concepts/event_graph_walker.mdx

@@ -120,15 +120,14 @@ Eg-Walker handles this by:
 
 | Aspect | Traditional CRDT | Eg-Walker |
 |--------|-----------------|-----------|
-| Per-operation metadata | 20-50 bytes | 4-8 bytes |
 | Tombstone storage | Permanent | Can be garbage collected |
 | Document growth | Linear with all operations | Linear with active operations |
 
 ### 2. **Faster Local Updates**
 
 - **No metadata computation**: Direct index-based operations
 - **No tombstone traversal**: Clean document state
-- **Predictable performance**: O(1) for most local operations
+- **Predictable performance**: O(1) or O(logN) for most local operations
 
 ### 3. **Efficient Synchronization**
 
@@ -184,18 +183,3 @@ The algorithm has been proven to:
 - Maintain strong eventual consistency
 - Preserve all CRDT correctness properties
 - Significantly reduce computational and storage overhead
-
-## Key Takeaways
-
-1. **Simplicity**: Replace complex metadata with simple indices
-2. **Efficiency**: Replay only what's necessary, when necessary
-3. **Scalability**: Bounded storage growth with safe garbage collection
-4. **Performance**: Fast local operations, efficient synchronization
-5. **Innovation**: Fundamental rethinking of CRDT implementation
-
-Eg-Walker represents a breakthrough in collaborative editing technology, making CRDTs more practical and performant for real-world applications. While Loro is not a strict Eg-Walker implementation, it has been profoundly influenced by Eg-Walker's design philosophy and achieves many of the same benefits through this inspiration. By cleverly leveraging the causal history already present in collaborative systems, both Eg-Walker and Loro-inspired approaches achieve the seemingly impossible: simpler data structures with better performance.
-
-[Lamport]: https://en.wikipedia.org/wiki/Lamport_timestamp
-[Fugue]: https://arxiv.org/abs/2305.00583
-[RGA algorithm]: https://www.sciencedirect.com/science/article/abs/pii/S0743731510002716
-[Yjs]: https://github.com/yjs/yjs