,
tags. For "Clear Signing" keep as is but maybe add quotation marks or italics? In Finnish, often use "Clear Signing" or selkeä allekirjoitus? But requirement says keep proper nouns in original form. So keep "Clear Signing" in English. Also "Ethereum Foundation" -> "Ethereum-säätiö" (common translation). "MetaMask", "Rabby", "Safe" are proper names, keep. "DeFi" keep. "L2s" -> "L2-ratkaisut" or keep L2? Better to keep L2 as is, but explain? Not necessary. "ice fishing" -> "jääkalastus" but it's a term, maybe keep "ice fishing" in quotes? Actually "ice fishing" is a type of phishing, maybe translate as "jääkalastus" but it's not common. Better to keep as 'ice fishing' in English.
Meta description: "Ethereum Foundation announces Clear Signing standard to combat billions in phishing losses. The new format translates transaction data into plain language for safer approvals." -> "Ethereum-säätiö ilmoittaa Clear Signing -standardista torjumaan miljardien tietojenkalastelutappioita. Uusi muoto kääntää transaktiodatan selkokielelle turvallisempia hyväksyntöjä varten."
Now write the full JSON. Ensure valid JSON. Use double quotes. Escape any inner quotes. The content is HTML, so we need to put it as a string. Be careful with line breaks? It's fine to have a single line string. But for readability, we can keep it as a multiline string in JSON? JSON does not allow literal newlines in strings; we must use \n. However, the instruction says "RESPOND IN JSON" and gives example with multiline. Usually, we can output pretty-printed JSON with newlines inside the string? That would be invalid. Better to output a single line string with proper escaping. But the example in the prompt shows the content as a multiline block. Actually the prompt says "RESPOND IN JSON:" and then shows a template with "content": "
