Address code review feedback: clarify geolocation alias and add QR code format descriptions

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Author: Copilot

content/docs/guides/field-types.mdx

@@ -687,10 +687,16 @@ ticket_code: Field.qrcode({
 ```
 
 **Supported Formats:**
-- `qr` - QR Code
-- `barcode` - Standard barcode
-- `ean13` - EAN-13 barcode
-- `code128` - Code 128 barcode
+- `qr` - QR Code (2D matrix barcode, best for URLs, text, and complex data)
+- `barcode` - Standard 1D barcode (linear format for simple numeric/text data)
+- `ean13` - EAN-13 barcode (13-digit product identifier, commonly used in retail)
+- `code128` - Code 128 barcode (high-density 1D format supporting full ASCII character set)
+
+**Use Cases:**
+- Product SKUs and inventory management (ean13, code128)
+- Event tickets and access control (qr)
+- Document tracking and verification (qr)
+- Shipping labels and logistics (code128)
 
 ---
 

content/docs/specifications/architecture/data-layer.mdx

@@ -34,7 +34,7 @@ Defines data properties with 35 types:
 - **Basic**: text, textarea, number, boolean, date, datetime
 - **Advanced**: lookup, master_detail, formula, summary, autonumber
 - **Rich**: email, phone, url, currency, percent, markdown, html, richtext
-- **Complex**: address, location, geolocation, file, image, avatar
+- **Complex**: address, location (aka geolocation), file, image, avatar
 - **Enhanced**: code, color, rating, slider, signature, qrcode
 
 ### 2. Query Protocol (`src/data/query/`)