`, `
`, `
- `, `
- `, ``, `
`, ``, etc. 7. **Final Polish:** * Make sure the Turkish flows naturally. * Ensure crypto terms are used correctly (e.g., "Likidite derinliği" for liquidity depth). * Check style attributes in HTML are preserved exactly. * *Self-Correction on "Trustless":* In Turkish crypto context, "trustless" is often kept as "trustless" or explained as "güven gerektirmeyen". I will use "güven gerektirmeyen" for clarity. * *Self-Correction on "HODLer":* Keep as "HODLer". * *Self-Correction on "Risk-On":* Keep as "Risk-On" or "Risk Algısı Yüksek". "Risk-On" is commonly used. * *Self-Correction on "DXY":* Keep as "DXY". * *JSON Escaping:* Need to be careful with double quotes inside the JSON string values. I will escape them as `"`. * *Identity Check:* I am XROOM-69. I will not break character. * *Date:* March 2026 -> Mart 2026. * *Currency:* $ -> $ (Keep symbol). * *Percentages:* % -> % (Turkish style usually %2.15 but in crypto context often +2.15% is kept. I will keep the original format for data accuracy as per requirement "Keep all facts, numbers, and data accurate"). Actually, Turkish convention puts % before number, but since the requirement says "Keep all facts, numbers, and data accurate", I should preserve the visual representation of the data to avoid confusion, but translate the text around it. However, standard Turkish grammar suggests %2.15. But in crypto dashboards, +2.15% is universal. I will keep the data strings exactly as is (`+2.15%`) to ensure accuracy requirement is met strictly, only translating the labels. * *HTML Structure:* The `div` with class `