Address code review feedback: improve documentation clarity

Co-authored-by: wannaphong <8536487+wannaphong@users.noreply.github.com>

Author: Copilot

MIGRATION.md

@@ -21,9 +21,10 @@ This aligns with the ISO/ANSI standard used in EU, UK, US, and the Unicode Brail
 ## Impact on Users
 
 ### For End Users
-- **No visible changes**: The Braille characters produced are identical
+- **Output changes**: The Unicode Braille characters will be different due to standardization
+- **Same semantic meaning**: The Braille patterns represent the same Thai text content, but using international standard encoding
 - **Same API**: All function signatures remain unchanged
-- **Same output**: `thai_word_braille()` and `thai_text_braille()` produce the same Unicode Braille characters
+- **Backward compatibility**: Existing code continues to work without modifications
 
 ### For Developers Working with Internal Representations
 If you were directly accessing or manipulating the internal dot pattern representations (e.g., in `thai_braille_mapping_dict` or the `Braille` class), you need to be aware of the new numbering:

thaibraille/text/core.py

@@ -12,6 +12,12 @@
 
 This follows the ISO/ANSI standard used internationally (EU, UK, US).
 The Unicode Braille Patterns block (U+2800-U+28FF) also uses this numbering.
+
+Data structures:
+  - thai_braille_mapping_dict: Maps Thai characters to lists of dot pattern strings
+    Example: "ก" -> ["1245"] means character ก uses dots 1, 2, 4, 5
+  - Braille.db: Maps dot pattern strings to Unicode Braille characters
+    Example: "1245" -> "⠛" (U+281B)
 """
 import re
 from pythainlp.util import Trie