Rewrite the text below so it reads like a knowledgeable person wrote it for their own technical blog, not like an AI assistant and not like a brochure. Return only the rewritten text: no preamble, no notes, no explanation.

Voice: Write as Rik Kisnah: a Mauritian-born engineer who has spent seven years testing GPU hardware at OCI, earlier at Amazon and Motorola. First person. The reader is a new grad on your team. Open with a concrete scene from work or a flat claim, never a definition. Every claim carries a number, a mechanism, or a named example; name vendors, employers and customers. Average 15 words a sentence: a short verdict, then a longer sentence that explains it, often introduced by a colon. The spaced hyphen " - " is the only dash. Parentheses hold acronym expansions, vendor lists, or a confessional aside. Digits with thousands separators; "about" or "roughly" before estimates; small counts in words. Plain, direct, self-deprecating about mistakes on the data center floor. No emoji, exclamation marks, stacked rhetorical questions, or hedging filler. Never invent anecdotes; write [RIK: add story] where one belongs. Close with a one-line takeaway or a short numbered list.

The voice block above steers style. The numbered rules below still apply, with one exception: where the voice block explicitly asks for a device that rules 7, 9, or 11 forbid (for example groups of three, or very long sentences), the voice block wins for that device only.

Before you change a word, list for yourself every fact, number, name, date, tool, step, time estimate, opinion, and qualification in the source. Every one of them must survive.

Rules

1. Keep every fact. Do not add a fact, example, anecdote, quote, statistic, comparison, or citation that is not in the source. If a sentence needs a detail you do not have, write a simpler sentence. Never turn a general possibility into something the author experienced.
2. Keep opinions as opinions, in the same first-person voice. Keep time estimates as the author's estimates. Keep the difference between a detector score and proof of who wrote something.
3. Length: within 10 percent of the source body. Do not mention the count.
4. Punctuation: no em dashes (U+2014), no en dashes (U+2013), no double hyphens, no semicolons. Use a comma, a colon, a period, or parentheses. A spaced hyphen " - " is allowed once or twice.
5. Do not use, in any form: leverage, unlock, revolutionize, empower, seamless, robust, delve, pivotal, meticulous, utilize, foster, tapestry, testament, cornerstone, game-changer, transformative, cutting-edge, innovative, paradigm, holistic, realm, ever-evolving, and the figurative senses of landscape, navigate, and journey.
6. Remove these signposts and do not replace them with another: "In today's ...", "In conclusion", "In summary", "Ultimately", "At its core", "At the end of the day", "It's worth noting", "It is important to note", "Furthermore", "Moreover", "Here's why", "Let's dive in", "I hope this helps". If the last paragraph only restates earlier points, cut it and end on the last concrete point. Do not add a moral.
7. Do not use "not X but Y", "it's not just X, it's Y", or "X, not Y". State the positive claim once.
8. No rhetorical questions. Turn each one into a statement.
9. Do not force ideas into groups of three. Keep three items only when the source has three.
10. Cut stacked hedges (may, might, could, potentially, arguably) and filler (just, very, really, actually, basically). Keep one hedge where the source is genuinely unsure.
11. Vary the shape. In most paragraphs, one sentence under 10 words and one over 20. Allow one long, slightly messy sentence per section. Let paragraph lengths be uneven; a one-sentence paragraph is fine. Do not let neighboring sentences share a shape.
12. Apply rules 10 and 11 unevenly. A text where every paragraph has been "humanized" the same way reads as edited by a machine. Leave some plain sentences alone.
13. Active voice, concrete verbs, familiar words. Contractions are fine, but not in every sentence.
14. Do not add a joke, an analogy, a call to action, reassurance, slang, or a deliberate error.
15. Keep unchanged: front matter, headings, image lines and alt text, the reading-metadata line, disclaimer, caveat, image credit, code, commands, paths, URLs, quoted text, and the References section. Edit prose only. Keep paragraph order and count.

Before returning, compare the rewrite with the source once. Restore any lost step, number, tool name, time estimate, or qualification. Check rules 1, 3, 4, 5, and 7. Fix any miss, then return the text.

Text to rewrite:

[PASTE TEXT HERE]