news headline, not analysis. Output JSON with title, slug, content (HTML), meta description, keyword

And

." That seems like a placeholder. Let's look: "ORIGINAL CONTENT:

And

. Meta description: 150-160 chars. Something like: ..." So it's a mix of instructions and a partial article? Actually, the user wrote: "ORIGINAL CONTENT:

And

. Meta description: 150-160 chars. Something like: ..." So it seems they are giving us the meta description and some notes, but not the actual article content. Maybe they expect us to write the article ourselves based on the facts? But the task is translation. Perhaps the original article is missing and we need to translate the given meta description and then generate the content? That doesn't make sense. Given the confusion, I think the user intended to provide an article but accidentally gave a description. However, the instruction says "Translate this article to Finnish" and then provides a "ORIGINAL CONTENT" that is actually a meta description and some guidelines. So perhaps the "ORIGINAL CONTENT" is the article? But it's not in proper HTML. It starts with "

And

." which is incomplete. Maybe they meant to paste the article but it got cut off. Alternatively, the user might be asking us to create a Finnish version of an article based on the given facts, but they explicitly say "Translate" so we should translate the given text. But the given text is not an article; it's a description of what the article should be. Let's interpret the user's request: They want a JSON output with title, slug, content (HTML), meta description, keyword. The "ORIGINAL CONTENT" is the source text to translate. But that source text is the paragraph we see. So we need to translate that paragraph into Finnish? That would be odd because it's not an article. However, the paragraph includes "Meta description: 150-160 chars. Something like: ..." So it's a set of instructions. Maybe the user wants us to translate the meta description and also generate the article content in Finnish based on the facts. But the instruction says "Translate this article" - so we must assume the article is the content we need to produce. Perhaps the user has provided the facts and expects us to write an article in Finnish based on those facts. But that's not translation; that's creation. Given the ambiguity, I'll assume that the "ORIGINAL CONTENT" is the article text that needs translation, but it's incomplete. However, the user explicitly says "ORIGINAL CONTENT:

And

." That suggests they started to paste an article but only included the first tags. Then they went on to describe the meta description. So maybe the actual article is missing. Alternatively, perhaps the user wants us to translate the meta description and also create the article content based on the given facts, but they want the output in Finnish. The instruction says "Translate this article" but there is no article. Given the lack of clarity, I'll take a pragmatic approach: I'll create a Finnish version of an article about the CNET test on airplane mode charging, using the facts provided (4-11 minutes savings, debunking the 25% claim, powering down works better). I'll write an article in Finnish, with proper HTML structure, and also provide a translated meta description in Finnish. The title should be a news headline in Finnish. The slug would be a URL-friendly version. The keyword would be "airplane mode charging" or something. But the user specifically said "Translate this article" - so maybe they expect us to translate the given text? However, the given text is not an article. Let's see if we can parse the given text as an article: It says "ORIGINAL CONTENT:

And

." That is not valid. Then it says "Meta description: 150-160 chars. Something like: ..." So it's a description. I think the best course is to respond with a JSON that contains a Finnish translation of the meta description and a Finnish article based on the facts. But the user might have intended to provide the article text. Since it's missing, I'll generate the article content in Finnish based on the facts and the meta description they provided. I'll also translate the meta description into Finnish. To be safe, I'll include a note? But the instruction says to respond in JSON only. So I'll produce the JSON. Let's craft the Finnish article. The original facts: CNET tested airplane mode charging, found savings of 4-11 minutes, not the claimed 25%. Powering down the phone works better. I'll write a short news article in Finnish. Use proper HTML:

with

for subheadings,

paragraphs. Title: "CNET:n testi: Lentokonetila ei nopeuta latausta niin paljon kuin väitetään" or something. But we need a news headline. Maybe "Lentokonetila latauksen aikana säästää vain 4–11 minuuttia – CNET:n testi kumoaa 25 prosentin väitteen" Meta description in Finnish: Need 150-160 characters. Translate the English one we crafted: "CNET:n lataustestit osoittavat, että lentokonetila säästää vain 4–11 minuuttia, mikä kumoaa 25 prosentin väitteen. Virran sammuttaminen on nopeampi vaihtoehto. Katso luvut itse." Let's count characters: "CNET:n lataustestit osoittavat, että lentokonetila säästää vain 4–11 minuuttia, mikä kumoaa 25 prosentin väitteen. Virran sammuttaminen on nopeampi vaihtoehto. Katso luvut itse." - let's count: C-N-E-T-:-n (6? Actually "CNET:n" is 6 including colon? Let's write: "CNET:n" = C,N,E,T,:,n? That's 6 characters? Actually "CNET:" is 5, then n? No, "CNET:n" is C N E T : n = 6. Then space (1) =7, "lataustestit" = 12? L-a-t-a-u-s-t-e-s-t-i-t = 12? Actually "lataustestit" is 12? Let's count: l a t a u s t e s t i t = 12. So 7+12=19, space=20, "osoittavat" = 9? o s o i t t a v a t = 10? Actually "osoittavat" is 10? Let's do systematically. But we can just approximate. We'll ensure it's 150-160. I'll write a concise one. Alternatively, we can use: "CNET:n testit osoittavat, että lentokonetila säästää vain 4–11 minuuttia latauksessa, ei väitettyä 25 prosenttia. Sammuttamalla puhelimen lataus on nopeampaa." That might be