TEAMGROUP T-FORCE VULCAN Z 32GB (32GBX1) DDR4 3200MHZ RED DESKTOP RAM

2. **Analyze the Input Text:**
The input is already structured as HTML with `` and `
` tags. It lists technical specs:
- Brand: Crucial
- Manufacturer: Crucial, Micron Consumer Products Group, ...
- Series: Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory
- Colour: Black
- Form Factor: DIMM
- Item Height: 34.8 Millimeters
- Item Width: 8 Millimeters
- Product Dimensions: 13.65 x 0.8 x 3.48 cm; 33 g
- Item model number: CP2K16G64C38U5B
- RAM Size: 32 GB

I need to clean this up. The rules say "If the text is already clean, return it as-is with minimal changes." But also "Remove ALL marketing fluff, promotional language, and sales pitches." Looking at the text, it's mostly technical specs. There's a bit in "Series: Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory" - "Overclocking Desktop Gaming Memory" could be considered marketing fluff, but it's part of the series name. I should keep it factual. Maybe rephrase to remove promotional tone, but rules say "do NOT invent or change any data." So I should keep the data intact but maybe restructure into clean HTML with only allowed tags.

Wait, the input is already HTML with `` and `
`. The rules say output clean HTML using ONLY

, ,
. The input already uses only those tags (plus the content). So maybe I just need to ensure it complies, maybe remove any unnecessary fluff, but keep data.

Let's check each line:
- `Brand: Crucial` - fine
- `Manufacturer: Crucial, Micron Consumer Products Group, Division of Micron Semiconductor Asia Operations Pte Ltd, 1 North Coast Drive, Singapore, 757432` - fine, technical
- `Series: Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory` - "Overclocking Desktop Gaming" could be seen as marketing, but it's part of the series description. I might keep it or strip "Gaming" if it's fluff, but rules say don't change data. I'll keep it as-is but maybe rephrase to be purely technical? Actually, "Pro DDR5 RAM 6400MHz" is technical. "Overclocking Desktop Gaming Memory" is descriptive but could be considered fluff. I'll keep it conservative.
- `Colour: Black` - fine
- `Form Factor: DIMM` - fine
- `Item Height: 34.8 Millimeters` - fine
- `Item Width: 8 Millimeters` - fine
- `Product Dimensions: 13.65 x 0.8 x 3.48 cm; 33 g` - fine
- `Item model number: CP2K16G64C38U5B` - fine
- `RAM Size: 32 GB` - fine

The input already uses only `` and `
`. The rules say output using ONLY

, ,
. So I can wrap in `

` if needed, but the input is already valid. However, the user says "Clean this short product description. Output clean HTML with

, ,
tags only:" and provides the input. I need to output the cleaned version.

Since the input is already clean technically, and uses only allowed tags, I could return it as-is. But maybe I should combine into fewer sentences? Rule: "Keep it concise — 2-4 sentences maximum." The current input is a list of key-value pairs, not sentences. I need to output HTML that represents the description concisely, 2-4 sentences max. So I need to condense the specs into 2-4 sentences, using only

, ,
.

Let me re-read carefully: "Your job is to CLEAN and BEAUTIFY the short product description for a WooCommerce product page." "Rules: 1. Remove ALL marketing fluff... 2. Keep technical accuracy... 3. Output clean HTML using ONLY these tags:

, ,
. 4. Do NOT use ... 5. If the text is already clean, return it as-is with minimal changes. 6. Do NOT add any preamble... 7. Keep it concise — 2-4 sentences maximum."

There's a tension between "if already clean, return as-is" and "keep it concise 2-4 sentences max." The input is a list of specs, not sentences. I think I need to condense it into 2-4 sentences of clean HTML, keeping all technical data accurately, removing fluff.

How to condense? I can create sentences that include multiple specs. But I must not invent or change data. I can group them logically.

Possible output:

Brand: Crucial, Model: CP2K16G64C38U5B, Capacity: 32 GB DDR5-6400 UDIMM CL38

But that changes structure. Maybe better to keep the key-value pairs but in sentence form? Actually, I can use for labels and normal text for values, with
between sentences.

Let me think of a way to present 2-4 sentences that cover all technical facts without fluff. Each sentence can have multiple tags for labels.

Sentence 1: This RAM is a Crucial Pro 32 GB kit (2x16GB) DDR5-6400 UDIMM with CL38 latency, model CP2K16G64C38U5B.
Sentence 2: It features a DIMM form factor, 34.8mm height, 8mm width, and dimensions of 13.65 x 0.8 x 3.48 cm weighing 33g.

But I need to include manufacturer, series, colour, etc. Maybe 3-4 sentences.

However, rule 5 says "If the text is already clean, return it as-is with minimal changes." The input text is already using only and
, no fluff really. Maybe I should just return it as-is, or very minimally adjusted. But rule 7 says keep it concise 2-4 sentences max. The input isn't sentences. I need to interpret this correctly.

Perhaps the user expects me to take the spec list and turn it into clean HTML paragraph(s) with 2-4 sentences, using the allowed tags, removing any unnecessary stuff. The input already has no marketing fluff, but it's a list. I'll condense it into 2-4 sentences.

Let me draft:

Brand: Crucial Series: Pro DDR5 RAM 6400MHz Model: CP2K16G64C38U5B Capacity: 32 GB

Form Factor: DIMM Colour: Black Dimensions: 13.65 x 0.8 x 3.48 cm; 33 g Height: 34.8 mm Width: 8 mm

That's 2 sentences (wrapped in

). But does it keep all data accurately? Yes. Is it concise? Yes, 2 sentences. Does it use only allowed tags? Yes. No fluff.

Wait, the original has "Manufacturer:" and "Item model number:" etc. I should include all technical specs. Maybe 3 sentences.

Let me list all specs from input:
- Brand: Crucial
- Manufacturer: Crucial, Micron Consumer Products Group, Division of Micron Semiconductor Asia Operations Pte Ltd, 1 North Coast Drive, Singapore, 757432
- Series: Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory
- Colour: Black
- Form Factor: DIMM
- Item Height: 34.8 Millimeters
- Item Width: 8 Millimeters
- Product Dimensions: 13.65 x 0.8 x 3.48 cm; 33 g
- Item model number: CP2K16G64C38U5B
- RAM Size: 32 GB

I need to output clean HTML with only

, ,
. I'll make 3 sentences, each a

, using for labels.

Sentence 1: Brand, model, capacity, series.
Sentence 2: Form factor, colour, dimensions, weight.
Sentence 3: Height, width, manufacturer.

But "Overclocking Desktop Gaming Memory" in series - I'll keep it as-is since it's data, though it has marketing tone. Rule 1 says remove ALL marketing fluff. "Overclocking Desktop Gaming" could be considered fluff, but it's part of the series name. I might rephrase to "DDR5 RAM 6400MHz" and omit the gaming part, but that changes data. I'll keep it exactly as input to be safe, since "do NOT invent or change any data."

Actually, re-reading rule 1: "Remove ALL marketing fluff, promotional language, and sales pitches." The series text "Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory" contains "Overclocking Desktop Gaming" which is marketing fluff. But if I remove it, I'm changing data. The rule says "Keep technical accuracy — do NOT invent or change any data." So I should keep the exact text, as it's given. Or maybe I can strip "Gaming" if it's fluff, but I'm not sure. To be safe, I'll keep the exact strings.

Let me just output the input as-is, since it already uses only and
, and has no other fluff. But rule 7 says keep it concise 2-4 sentences max. The input is not sentences. I need to decide.

Perhaps the best approach: condense into 2-4 sentences, keeping all data points as labels, removing the explicit "Sentence" structure but grouping. I'll output something like:

Brand: Crucial Manufacturer: Crucial, Micron Consumer Products Group, Division of Micron Semiconductor Asia Operations Pte Ltd, 1 North Coast Drive, Singapore, 757432 Series: Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory Colour: Black

Form Factor: DIMM Item Height: 34.8 Millimeters Item Width: 8 Millimeters Product Dimensions: 13.65 x 0.8 x 3.48 cm; 33 g Item model number: CP2K16G64C38U5B RAM Size: 32 GB

That's 2

sentences. All tags allowed. All data preserved. No fluff added. Minimal changes.

Wait, the user said "If the text is already clean, return it as-is with minimal changes." Maybe I should just return the input as-is. But then rule 7 about 2-4 sentences conflicts. Maybe the user expects me to clean it up into proper HTML paragraphs, but the input is already clean HTML. I'll re-read the prompt.

"Product context: ... Clean this short product description. Output clean HTML with

, ,
tags only: [input HTML]"

The input is already HTML with only and
. It might be considered already clean. But rule 7 says "Keep it concise — 2-4 sentences maximum." The input isn't sentences. I think I need to convert it to 2-4 sentences while keeping data.

Let me check if there's any marketing fluff to remove. "Overclocking Desktop Gaming Memory" - I could argue it's part of the series spec, but it's promotional. I'll keep it as-is to avoid changing data.

I'll output the input wrapped in

tags, maybe split into 2 paragraphs, keeping all and
. But the input already has
at the end of each line. If I output as-is, it's fine. But the user wants me to "Clean this short product description." Maybe they want me to remove the line breaks and make it proper paragraphs, but still using only allowed tags.

I'll produce 2

blocks, each containing multiple key-value pairs, separated by
if needed. But
is allowed. Actually, I can just output the same content but structured into 2 sentences. Let me draft carefully.

Option:

Brand: Crucial Manufacturer: Crucial, Micron Consumer Products Group, Division of Micron Semiconductor Asia Operations Pte Ltd, 1 North Coast Drive, Singapore, 757432 Series: Pro DDR5 RAM 6400MHz Overclocking Desktop Gaming Memory Colour: Black

Form Factor: DIMM Item Height: 34.8 Millimeters Item Width: 8 Millimeters Product Dimensions: 13.65 x 0.8 x 3.48 cm; 33 g Item model number: CP2K16G64C38U5B RAM Size: 32 GB

This is 2 sentences (each a

). It includes all data. Uses only

, ,
. No other tags. No fluff removed or added (I kept the series text as-is). Data accuracy maintained.

But wait, rule 5: "If the text is already clean, return it as-is with minimal changes." The input text is already clean HTML with only allowed tags. Maybe I should just return the input exactly as given. However, rule 7 explicitly says "Keep it concise — 2-4 sentences maximum." This suggests I need to condense it into sentences. The input is a list of key-value pairs with
, not sentences. I think the intent is for me to output clean HTML that represents the description concisely.

I'll go with the 2

sentences approach. It satisfies all rules: removes fluff (none present, kept as-is), keeps technical accuracy, uses only allowed tags, no preamble, concise 2 sentences.

Let me double-check the tags usage:

and and
. Yes. No