@maccesar/titools 2.2.4 → 2.2.9

package/skills/ti-expert/references/testing-unit.md

@@ -1,11 +1,11 @@
-# Unit Testing Guide for Titanium + Alloy
+# Unit testing guide for Titanium + Alloy
 
 > **OPTIONAL - Advanced Topic**
 > This guide covers automated testing, which is OPTIONAL for Titanium/Alloy projects.
 > Testing is useful for teams practicing CI/CD, projects with complex business logic, or refactoring confidence.
 > If you prefer manual testing on device, you can safely skip this guide.
 
-## What CAN Be Tested (Without Compiling)
+## What can be tested (Without Compiling)
 
 **Pure JavaScript Logic:**
 - Services (authService, navigationService, etc.)
@@ -13,7 +13,7 @@
 - Business logic (calculations, data transformations)
 - Models (with mocked database)
 
-## What CANNOT Be Easily Tested
+## What cannot be easily tested
 
 **Requires Compiled App:**
 - Controllers (UI interactions)
@@ -23,11 +23,11 @@
 
 ---
 
-## Testing Philosophy
+## Testing philosophy
 
 **Test behavior, not implementation.** Focus on what the code does from the outside, not how it achieves it internally.
 
-## Project Structure
+## Project structure
 
 ```
 app/
@@ -52,9 +52,9 @@ app/
 │   │   └── setup.js         # Test environment setup
 ```
 
-## Writing Testable Code
+## Writing testable code
 
-### Dependency Injection for Testability
+### Dependency injection for testability
 
 ```javascript
 // BAD: Hard to test - direct dependency
@@ -86,7 +86,7 @@ describe('getUser', () => {
 })
 ```
 
-## Unit Testing Services
+## Unit testing services
 
 ```javascript
 // specs/unit/services/authService.spec.js
@@ -147,7 +147,7 @@ describe('AuthService', () => {
 })
 ```
 
-## Unit Testing Helpers
+## Unit testing helpers
 
 ```javascript
 // specs/unit/helpers/i18n.spec.js
@@ -184,7 +184,7 @@ describe('i18n Helper', () => {
 })
 ```
 
-## Integration Testing Controllers
+## Integration testing controllers
 
 ```javascript
 // specs/integration/controllers/login.spec.js
@@ -270,7 +270,7 @@ describe('Login Controller', () => {
 })
 ```
 
-## Mock Factory
+## Mock factory
 
 ```javascript
 // lib/testing/mocks.js
@@ -326,7 +326,7 @@ exports.Mocks = {
 }
 ```
 
-## Test Helper Functions
+## Test helper functions
 
 ```javascript
 // lib/testing/helpers.js
@@ -373,7 +373,7 @@ exports.TestHelpers = {
 }
 ```
 
-## Test Setup Configuration
+## Test setup configuration
 
 ```javascript
 // lib/testing/setup.js
@@ -396,7 +396,7 @@ afterAll(() => {
 })
 ```
 
-## Running Tests
+## Running tests
 
 ```bash
 # Run specific test suite
@@ -409,18 +409,18 @@ titanium test --coverage
 titanium test --specs app/specs/unit/services/authService.spec.js
 ```
 
-## Anti-Patterns to Avoid
+## Anti-patterns to avoid
 
-| Anti-Pattern               | Problem                        | Solution                        |
+| Anti-Pattern | Problem | Solution |
 | -------------------------- | ------------------------------ | ------------------------------- |
-| Testing private methods    | Breaks on refactoring          | Test public interface only      |
-| Mocking everything         | Tests pass, code fails         | Mock only external dependencies |
-| No cleanup in tests        | Memory leaks, interference     | Always cleanup in afterEach     |
-| Testing XML/TSS            | Fragile, implementation detail | Test rendered behavior instead  |
-| Hard dependencies          | Untestable code                | Use dependency injection        |
-| Shared state between tests | Flaky tests                    | Reset state in beforeEach       |
-
-## Test Checklist
+| Testing private methods | Breaks on refactoring | Test public interface only |
+| Mocking everything | Tests pass, code fails | Mock only external dependencies |
+| No cleanup in tests | Memory leaks, interference | Always cleanup in afterEach |
+| Testing XML/TSS | Fragile, implementation detail | Test rendered behavior instead |
+| Hard dependencies | Untestable code | Use dependency injection |
+| Shared state between tests | Flaky tests | Reset state in beforeEach |
+
+## Test checklist
 
 Before committing code, verify:
 

package/skills/ti-expert/references/theming.md

@@ -1,10 +1,10 @@
-# Theming & Dark Mode
+# Theming & dark mode
 
-## Alloy Theme System
+## Alloy theme system
 
 Alloy has a built-in theme system via the `app/themes/` folder. Themes override views, styles, and assets without modifying originals.
 
-### Theme Folder Structure
+### Theme folder structure
 
 ```
 app/
@@ -26,7 +26,7 @@ app/
 ├── config.json
 ```
 
-### Activating a Theme
+### Activating a theme
 
 Set the theme in `config.json`:
 
@@ -45,7 +45,7 @@ Set the theme in `config.json`:
 Alloy themes are applied at **build time**. You cannot switch themes at runtime using this system alone. For runtime switching, use the Dynamic Theming approach below.
 :::
 
-### Theme Cascade
+### Theme cascade
 
 When a theme is active, Alloy merges files in this order:
 1. `app/styles/app.tss` (base)
@@ -53,15 +53,15 @@ When a theme is active, Alloy merges files in this order:
 3. `app/styles/<controller>.tss` (controller-specific)
 4. `app/themes/<theme>/styles/<controller>.tss` (theme + controller override)
 
-Theme files **merge** with base files — you only need to include properties you want to override.
+Theme files **merge** with base files , you only need to include properties you want to override.
 
 ---
 
-## Dynamic Theming with Alloy.Globals
+## Dynamic theming with Alloy.Globals
 
 For runtime theme switching (including Dark Mode), use `Alloy.Globals` as a centralized color palette.
 
-### Step 1: Define Color Palette
+### Step 1: define color palette
 
 ```javascript
 // alloy.js
@@ -98,7 +98,7 @@ Alloy.Globals.theme = themes[savedTheme]
 Alloy.Globals.themeName = savedTheme
 ```
 
-### Step 2: Use in TSS with Alloy.Globals
+### Step 2: use in TSS with Alloy.Globals
 
 ```tss
 /* app.tss - Global base styles using theme colors */
@@ -134,7 +134,7 @@ Alloy.Globals.themeName = savedTheme
 }
 ```
 
-### Step 3: Theme Switching Service
+### Step 3: theme switching service
 
 ```javascript
 // lib/services/themeService.js
@@ -176,7 +176,7 @@ exports.ThemeService = {
 }
 ```
 
-### Step 4: Respond to Theme Changes in Controllers
+### Step 4: respond to theme changes in controllers
 
 :::warning Theme change requires UI rebuild
 Since TSS is applied at controller creation time, changing `Alloy.Globals.theme` does NOT retroactively update already-rendered views. You must manually update visible elements or restart the root controller.
@@ -233,7 +233,7 @@ $.cleanup = cleanup
 
 ---
 
-## System Dark Mode Detection
+## System dark mode detection
 
 ### iOS 13+ / Android 10+
 
@@ -263,7 +263,7 @@ exports.ThemeService = {
 }
 ```
 
-### Semantic Colors (Cross-Platform)
+### Semantic colors (Cross-Platform)
 
 Titanium provides a cross-platform semantic colors API for Dark Mode support. Define colors in a `semantic.colors.json` file:
 
@@ -329,7 +329,7 @@ $.container.backgroundColor = 'backgroundColor';
 
 ---
 
-## Reusable Style Classes Pattern
+## Reusable style classes pattern
 
 Define a library of reusable TSS classes in `app.tss` for consistency across the app:
 
@@ -410,7 +410,7 @@ Define a library of reusable TSS classes in `app.tss` for consistency across the
 ".mx-lg": { left: 24, right: 24 }
 ```
 
-### Using Style Classes in Views
+### Using style classes in views
 
 ```xml
 <Alloy>

package/skills/ti-guides/SKILL.md

@@ -5,77 +5,75 @@ argument-hint: "[topic]"
 allowed-tools: Read, Grep, Glob, Edit, Write, Bash(node *)
 ---
 
-# Titanium SDK Guide Expert
+# Titanium SDK guide expert
 
-This skill ensures Titanium projects follow TiDev standards for stability, performance, and cross-platform reliability.
+Use this skill to keep Titanium projects aligned with TiDev standards for stability, performance, and cross-platform behavior.
 
-## Project Detection
+## Project detection
 
-:::info AUTO-DETECTS TITANIUM PROJECTS
-This skill automatically detects Titanium projects when invoked and provides SDK-specific guidance.
+:::info Auto-detects Titanium projects
+This skill auto-detects Titanium projects. No manual command is needed.
 
-**Detection occurs automatically** - no manual command needed.
-
-**Titanium project indicator:**
+Titanium project indicator:
 - `tiapp.xml` file (definitive indicator)
 
-**Applicable to BOTH:**
-- **Alloy projects** (app/ folder)
-- **Classic projects** (Resources/ folder)
+Applies to both:
+- Alloy projects (`app/` folder)
+- Classic projects (`Resources/` folder)
 
-**Behavior based on detection:**
-- **Titanium detected** → Provides official Titanium SDK guidance, memory management best practices, app distribution help
-- **Not detected** → Indicates this is for Titanium projects only
+Behavior:
+- If a Titanium project is detected, provide official Titanium SDK guidance, memory management best practices, and app distribution help.
+- If not detected, say this skill is only for Titanium projects.
 :::
 
-## Core Workflow
-
-1.  **Architecture Check**: Validate that the project follows a modular pattern (CommonJS or Alloy).
-2.  **Memory Review**: Ensure all global listeners are removed and heavy objects are nulled during cleanup.
-3.  **Bridge Optimization**: Identify and cache frequently accessed native properties to minimize bridge crossings.
-4.  **Native Integration**: Use Hyperloop for specialized native functionality, ensuring proper casting and thread management.
-5.  **Asset Management**: Optimize database operations with transactions and manage image memory footprints.
-
-## Procedural Rules (Low Freedom)
-
--   **Memory Hygiene**: Always remove `Ti.App` and `Ti.Geolocation` listeners in the controller cleanup phase.
--   **No Bridge Calls in Loops**: Never access `Ti.Platform` or `Ti.DisplayCaps` inside loops; store values in local variables.
--   **Hyperloop Naming**: Concatenate selectors accurately (e.g., `addAttribute:value:range:` -> `addAttributeValueRange`).
--   **DB Persistence**: Always close resultsets and database handles after every transaction block.
-
-## Reference Guides (Progressive Disclosure)
-
--   **[Hello World](references/hello-world.md)**: Project creation, structure, and getting started with Alloy or Classic Titanium.
--   **[JavaScript Primer](references/javascript-primer.md)**: JavaScript fundamentals, learning resources, best practices, and ES6+ features.
--   **[Application Frameworks](references/application-frameworks.md)**: Alloy vs Classic Titanium, architectural patterns, and framework selection.
--   **[Coding Best Practices](references/coding-best-practices.md)**: Memory leaks, bridge efficiency, event naming, security, and lazy loading.
--   **[CommonJS Advanced](references/commonjs-advanced.md)**: Stateful modules, caching, ES6+ support, and antipatterns.
--   **[Advanced Data & Images](references/advanced-data-and-images.md)**: SQLite transactions and image memory optimization.
--   **[Hyperloop Native Access](references/hyperloop-native-access.md)**: Objective-C/Swift/Java syntax, casting, debugging, XIB/Storyboards.
--   **[Style & Conventions](references/style-and-conventions.md)**: Naming standards and formatting rules.
--   **[Reserved Words](references/reserved-words.md)**: ECMAScript, iOS, and Alloy reserved keywords to avoid.
--   **[Alloy CLI Reference](references/alloy-cli-advanced.md)**: extract-i18n, code generation, and build hooks.
--   **[Alloy Data Mastery](references/alloy-data-mastery.md)**: Sync adapters, data binding, and Backbone collections.
--   **[Alloy Widgets & Themes](references/alloy-widgets-and-themes.md)**: Widget structure, styling priorities, and theming.
--   **[Android Manifest](references/android-manifest.md)**: Custom AndroidManifest.xml, permissions, and manifest merge.
--   **[App Distribution](references/app-distribution.md)**: Google Play (APK/AAB), App Store (IPA), certificates, provisioning, and deployment.
--   **[tiapp.xml Configuration](references/tiapp-config.md)**: Complete reference for tiapp.xml and timodule.xml, including all elements, properties, and platform-specific settings.
--   **[CLI Reference](references/cli-reference.md)**: Titanium CLI commands, options, tasks, configuration, and build processes.
--   **[Resources](references/resources.md)**: Community support, modules, sample code, Slack, and learning materials.
-
-## Related Skills
+## Core workflow
+
+1. Validate the project follows a modular pattern (CommonJS or Alloy).
+2. Ensure global listeners are removed and heavy objects are nulled during cleanup.
+3. Cache frequently accessed native properties to reduce bridge crossings.
+4. Use Hyperloop for specialized native functionality and handle casting and threading correctly.
+5. Use transactions for database work and manage image memory footprints.
+
+## Procedural rules
+
+- Always remove `Ti.App` and `Ti.Geolocation` listeners during controller cleanup.
+- Do not access `Ti.Platform` or `Ti.DisplayCaps` inside loops. Store values in local variables.
+- Concatenate Hyperloop selectors accurately (for example, `addAttribute:value:range:` -> `addAttributeValueRange`).
+- Close resultsets and database handles after every transaction block.
+
+## Reference guides
+
+- Hello World (references/hello-world.md): project creation, structure, and getting started with Alloy or Classic Titanium.
+- JavaScript Primer (references/javascript-primer.md): JavaScript fundamentals, learning resources, best practices, and ES6+ features.
+- Application Frameworks (references/application-frameworks.md): Alloy vs Classic Titanium, architectural patterns, and framework selection.
+- Coding Best Practices (references/coding-best-practices.md): memory leaks, bridge efficiency, event naming, security, and lazy loading.
+- CommonJS Advanced (references/commonjs-advanced.md): stateful modules, caching, ES6+ support, and antipatterns.
+- Advanced Data & Images (references/advanced-data-and-images.md): SQLite transactions and image memory optimization.
+- Hyperloop Native Access (references/hyperloop-native-access.md): Objective-C/Swift/Java syntax, casting, debugging, XIB/Storyboards.
+- Style & Conventions (references/style-and-conventions.md): naming standards and formatting rules.
+- Reserved Words (references/reserved-words.md): ECMAScript, iOS, and Alloy reserved keywords to avoid.
+- Alloy CLI Reference (references/alloy-cli-advanced.md): extract-i18n, code generation, and build hooks.
+- Alloy Data Mastery (references/alloy-data-mastery.md): sync adapters, data binding, and Backbone collections.
+- Alloy Widgets & Themes (references/alloy-widgets-and-themes.md): widget structure, styling priorities, and theming.
+- Android Manifest (references/android-manifest.md): custom AndroidManifest.xml, permissions, and manifest merge.
+- App Distribution (references/app-distribution.md): Google Play (APK/AAB), App Store (IPA), certificates, provisioning, and deployment.
+- tiapp.xml Configuration (references/tiapp-config.md): complete reference for tiapp.xml and timodule.xml, including all elements, properties, and platform-specific settings.
+- CLI Reference (references/cli-reference.md): Titanium CLI commands, options, tasks, configuration, and build processes.
+- Resources (references/resources.md): community support, modules, sample code, Slack, and learning materials.
+
+## Related skills
 
 For tasks beyond SDK fundamentals, use these complementary skills:
 
-| Task                                     | Use This Skill |
-| ---------------------------------------- | -------------- |
-| Project architecture, services, patterns | `ti-expert`    |
-| Native features (location, push, media)  | `ti-howtos`    |
-| Alloy CLI, configuration, debugging      | `alloy-howtos` |
-| UI layouts, ListViews, gestures          | `ti-ui`        |
+| Task | Use this skill |
+| --- | --- |
+| Project architecture, services, patterns | `ti-expert` |
+| Native features (location, push, media) | `ti-howtos` |
+| Alloy CLI, configuration, debugging | `alloy-howtos` |
+| UI layouts, ListViews, gestures | `ti-ui` |
 
-## Response Format
+## Response format
 
-1.  **Technical Recommendation**: Cite the specific TiDev best practice.
-2.  **Optimized Implementation**: Provide modern ES6+ code without semicolons.
-3.  **Rationale**: Briefly explain the performance or memory impact.
+1. Technical recommendation: cite the specific TiDev best practice.
+2. Optimized implementation: provide modern ES6+ code without semicolons.
+3. Rationale: briefly explain the performance or memory impact.

package/skills/ti-guides/references/advanced-data-and-images.md

@@ -1,9 +1,9 @@
-# Advanced Database and Image Best Practices
+# Advanced database and image best practices
 
-## 1. SQLite Optimization
+## 1. SQLite optimization
 
-- **Close Everything**: Always `resultSet.close()` and `db.close()` after each operation to avoid locks and memory bloat. SQLite enforces sequential write-access — if you don't close after `INSERT` or `UPDATE`, you may receive **DatabaseObjectNotClosed** exceptions on the next write attempt.
-- **Transactions**: Use `BEGIN` and `COMMIT` for batch inserts. It is significantly faster. Note: if any update within the transaction fails, the **entire batch is rolled back** (atomicity).
+- Close result sets and the database after each operation to avoid locks and memory growth. SQLite allows one writer at a time, and leaving a connection open after `INSERT` or `UPDATE` can trigger `DatabaseObjectNotClosed` on the next write.
+- Use transactions for batch inserts. If any statement fails, SQLite rolls back the entire batch.
   ```javascript
   const db = Ti.Database.open('myDatabase');
   db.execute('BEGIN');
@@ -13,12 +13,12 @@
   db.execute('COMMIT');
   db.close();
   ```
-- **Database Skeleton**: Do not ship large pre-populated databases. Ship a "skeleton" and download data on first boot to reduce IPA/APK size. The `Resources` directory is read-only, so installing a database copies it to `applicationDataDirectory`, resulting in two copies on the device.
-  - **Android note**: In Android 2.2 and earlier, the installer could not uncompress assets over 1 MB. Workaround: rename the file with a `.mp3` extension to prevent `aapt` compression.
+- Do not ship large pre-populated databases. Ship a small skeleton and download data on first boot to reduce IPA/APK size. The `Resources` directory is read-only, so installing a database copies it to `applicationDataDirectory`, which creates two copies on the device.
+  - Android note: in Android 2.2 and earlier, the installer could not uncompress assets over 1 MB. One workaround was to rename the file with a `.mp3` extension to prevent `aapt` compression.
 
-### Database Version Management
+### Database version management
 
-Store a version number in your database to detect which version is installed and take action (create tables, alter columns) on upgrades. If you lack a version table, use `PRAGMA TABLE_INFO` to detect column presence:
+Store a version number in your database so you can detect upgrades and run migrations. If you do not have a version table, use `PRAGMA TABLE_INFO` to detect column presence:
 
 ```javascript
 const addColumn = (dbname, tblName, newFieldName, colSpec) => {
@@ -41,30 +41,30 @@ const addColumn = (dbname, tblName, newFieldName, colSpec) => {
 
 ---
 
-## 2. Image Format Selection
+## 2. Image format selection
 
 Choose the right format for each use case:
 
-| Format | Compression | Best For | Avoid For |
-| ------ | ----------- | -------- | --------- |
-| **PNG** | Lossless | Icons, text, line-art, buttons | Photos (file size) |
-| **JPG** | Lossy | Photographs | Text, icons, line drawings (artifacts) |
-| **GIF** | Lossless (256 colors) | Rarely appropriate | Almost everything — limited colors, proprietary, animated GIF not supported on all platforms |
+| Format | Compression | Best for | Avoid for |
+| --- | --- | --- | --- |
+| PNG | Lossless | Icons, text, line art, buttons | Photos (large files) |
+| JPG | Lossy | Photographs | Text, icons, line drawings (artifacts) |
+| GIF | Lossless (256 colors) | Rare cases | Most cases (limited colors, animated GIF not supported everywhere) |
 
-**For flip-book animations**: Use `ImageView.images` property with an array of PNG or optimized JPG files instead of animated GIFs.
+For flip-book animations, use `ImageView.images` with an array of PNG or optimized JPG files instead of animated GIFs.
 
 ---
 
-## 3. Image Memory Management
+## 3. Image memory management
 
-- **Memory Footprint**: A JPG is small on disk but consumes `width * height * 3 bytes` in RAM when decompressed. Each pixel uses 24 bits (8 bits per R/G/B channel).
+- A JPG is small on disk but expands to `width * height * 3 bytes` in RAM. Each pixel uses 24 bits (8 bits per R/G/B channel).
   - Example: `(640 × 480 × 3) / 1024 = 900 KB` in memory for a single image
   - Device RAM available to your app can be as low as 12 MB, shared with your code and the Titanium framework
-- **Unloading**:
-  - `view.remove(imageView)` — removes from view hierarchy, helps OS free memory
-  - `imageView = null` — releases the native proxy object
-- **Resizing**: Always resize images to their display dimensions via `imageAsResized` or `imageAsCropped` (both on `Ti.Blob`) before setting the `image` property. Don't display a 1024×768 image on a 640×480 screen.
-- **Placeholder**: Set the `defaultImage` property on ImageView to show a local placeholder while a remote image downloads:
+- Unloading:
+  - `view.remove(imageView)` removes it from the view hierarchy and lets the OS free memory
+  - `imageView = null` releases the native proxy object
+- Resizing: resize images to their display dimensions using `imageAsResized` or `imageAsCropped` (both on `Ti.Blob`) before setting the `image` property. Do not display a 1024×768 image on a 640×480 screen.
+- Placeholder: set `defaultImage` on ImageView to show a local placeholder while a remote image downloads:
   ```javascript
   const imageView = Ti.UI.createImageView({
     image: 'https://example.com/photo.jpg',
@@ -76,12 +76,12 @@ Choose the right format for each use case:
 
 ---
 
-## 4. Image Optimization Tools
+## 4. Image optimization tools
 
-Resize and compress images before including them in your app to minimize IPA/APK size and network usage.
+Resize and compress images before including them in your app to reduce IPA/APK size and network usage.
 
-| Platform | File Types | Tool |
-| -------- | ---------- | ---- |
+| Platform | File types | Tool |
+| --- | --- | --- |
 | Mac | PNG, JPG, GIF | ImageOptim |
 | Mac, Windows, Linux | PNG, JPG, GIF | ImageMagick |
 | Windows/DOS | PNG | PNGCrush |
@@ -89,21 +89,21 @@ Resize and compress images before including them in your app to minimize IPA/APK
 
 ---
 
-## 5. Caching Remote Images
+## 5. Caching remote images
 
 Remote images are cached automatically on iOS, Android, and Windows.
 
-**Platform differences:**
-- **Android**: Cache limited to **25 MB**, persists for the lifetime of the app (while installed)
-- **iOS**: Cache size not predetermined (no guaranteed size), cleared by iOS when device needs storage
+Platform differences:
+- Android: cache limited to 25 MB, persists for the lifetime of the app (while installed)
+- iOS: cache size not fixed, cleared by iOS when the device needs storage
 
 To manually clean the cache, delete files in `applicationCacheDirectory`.
 
-**Android 6+ requirement**: Call `Ti.Filesystem.requestStoragePermissions()` before loading remote images (runtime permissions).
+Android 6+ requirement: call `Ti.Filesystem.requestStoragePermissions()` before loading remote images.
 
-### Manual Caching Utility
+### Manual caching utility
 
-For critical assets, cache manually in `applicationDataDirectory` for predictability:
+For critical assets, cache manually in `applicationDataDirectory` for more predictable behavior:
 
 ```javascript
 const CacheUtils = {

package/skills/ti-guides/references/android-manifest.md

@@ -1,8 +1,8 @@
 # Custom AndroidManifest.xml
 
-For most Android manifest settings, use `tiapp.xml`. Only create a custom manifest when absolutely necessary.
+For most Android manifest settings, use `tiapp.xml`. Only create a custom manifest when you really need it.
 
-## Preferred Method: tiapp.xml
+## Preferred method: tiapp.xml
 
 Add manifest entries in `tiapp.xml` inside the `<android>` section:
 
@@ -30,13 +30,13 @@ Add manifest entries in `tiapp.xml` inside the `<android>` section:
 </android>
 ```
 
-## How Merging Works
+## How merging works
 
-- **Most elements**: Replaced by your entry
-- **`<application>` element**: Attributes are merged additively
-- **Activities/Services**: Added to existing ones
+- Most elements are replaced by your entry.
+- The `<application>` element is merged additively by attribute.
+- Activities and services are added to existing ones.
 
-## Custom Manifest (Rare Cases)
+## Custom manifest (rare cases)
 
 If you need full control, create `platform/android/AndroidManifest.xml`:
 
@@ -49,26 +49,26 @@ MyApp/
 └── tiapp.xml
 ```
 
-**Warning**: You must maintain this file manually through SDK updates.
+Warning: you must maintain this file manually through SDK updates.
 
-## Common Use Cases
+## Common use cases
 
-### Camera Permission
+### Camera permission
 ```xml
 <uses-permission android:name="android.permission.CAMERA" />
 ```
 
-### Hardware Requirements
+### Hardware requirements
 ```xml
 <uses-feature android:name="android.hardware.camera" android:required="false" />
 ```
 
-### Launch Mode
+### Launch mode
 ```xml
 <application android:launchMode="singleTask" />
 ```
 
-### Deep Links
+### Deep links
 ```xml
 <intent-filter>
     <action android:name="android.intent.action.VIEW" />
@@ -86,9 +86,9 @@ ti build -p android
 # Check: build/android/AndroidManifest.xml.gen
 ```
 
-## Enable Manifest Merge (CLI 7.0+)
+## Enable manifest merge (CLI 7.0+)
 
-If using custom manifest, enable merge in `tiapp.xml`:
+If you use a custom manifest, enable merge in `tiapp.xml`:
 
 ```bash
 ti config android.mergeCustomAndroidManifest true