CS 1.0: SD-2845: Remove redundant "Mg"

[HenrikHL]

User description

SD-2845: Remove redundant Mg from description

---

PR Type

Documentation

---

Description

• Remove redundant unit notation from CO2 emissions description

• Simplify metric from "t / Mg" to just "t"

---

Diagram Walkthrough

flowchart LR
  A["CO2 emissions description"] -- "Remove redundant Mg notation" --> B["Simplified to metric tonnes only"]

Loading

File Walkthrough

	Relevant files
Documentation	CS_v1.0.2.yaml Remove redundant Mg notation from CO2 description                cs/v1/CS_v1.0.2.yaml Removed redundant "Mg" unit notation from CO2 emissions field description Changed description from "metric tonnes (t / Mg)" to "metric tonnes (t)" Clarifies that the unit is metric tonnes without duplicate notation +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
🟢	🎫 #SD-2845 🟢 Update the `co2` field description to remove the redundant `/Mg` unit notation. Ensure the description states CO2 emissions are in metric tonnes `(t)` (not `(t / Mg)`).
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: Passed 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: Passed 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: Passed 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: Passed 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: Passed 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: Passed 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

[HenrikHL]

@emiliodcsa FYI

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[emiliodcsa]

looks good : )