Update README with specific tiles folder path

[friendlyantz]

User description

Clarified instructions for copying tiles folder.

---

PR Type

Documentation

---

Description

• Clarified tiles folder destination path in setup instructions

• Specified that tiles should be copied under maps directory

---

Diagram Walkthrough

flowchart LR
  A["README Instructions"] -- "Updated destination" --> B["Copy tiles to maps directory"]

Loading

File Walkthrough

	Relevant files
Documentation	README.md Clarify tiles folder destination path                                        README.md Updated step 3 instructions to specify tiles folder should be copied under maps directory on T-Deck's SD card Improved clarity of setup instructions for users +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Documentation Only: The PR only updates README instructions without adding or modifying code related to audit logging, so compliance cannot be assessed from the diff. Referred Code 3. **Copy the `tiles` folder to your T-Deck's SD card under `maps` directory ** Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: No Code Changes: This PR adjusts documentation text only and contains no new identifiers to evaluate for naming clarity. Referred Code 3. **Copy the `tiles` folder to your T-Deck's SD card under `maps` directory ** Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Not Applicable Here: The change is a README instruction update with no executable code, so error handling cannot be assessed. Referred Code 3. **Copy the `tiles` folder to your T-Deck's SD card under `maps` directory ** Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: No Runtime Errors: Documentation-only change provides no user-facing error handling to review for sensitive detail leakage. Referred Code 3. **Copy the `tiles` folder to your T-Deck's SD card under `maps` directory ** Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: No Logging Added: The PR does not introduce logging changes; thus secure logging practices cannot be evaluated from this diff. Referred Code 3. **Copy the `tiles` folder to your T-Deck's SD card under `maps` directory ** Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No Input Handling: Since only README text was modified, there are no input validation or data handling changes to assess for security. Referred Code 3. **Copy the `tiles` folder to your T-Deck's SD card under `maps` directory ** Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.