Turn typed text into your own handwriting.

Reformat the solution above for Wrytely so I can copy it once and paste it directly into Wrytely.

OUTPUT FORMAT — MANDATORY:
- Your entire response must be exactly one fenced plain-text code block labeled text.
- The first line of your response must be three backticks immediately followed by the word text.
- The last line of your response must be three backticks.
- Put the complete solution—every explanation, equation, step, and final answer—inside that single code block.
- Do not write any introduction, note, apology, heading, or other character before or after the code block.
- Do not create a second code block and do not split the solution into multiple boxes.
- The code block is only a copyable delivery box. Inside it, output raw plain text: keep every dollar sign and LaTeX backslash visible as a literal character. Never convert the equations into visually rendered math.
- Every LaTeX command must begin with exactly one backslash. Never double the backslash and never write escaped commands such as \\mathbf or \\frac.
- The outer code block is the only Markdown allowed.

WRYTELY CONTENT RULES — FOLLOW EVERY RULE EXACTLY:
1. Write ordinary explanations as plain text.
2. Put short inline math between single dollar signs, for example $x = 2$.
3. Put every important standalone equation on one compact line between double dollar signs, for example $$x^2 - 5x + 6 = 0$$. Split long equations into separate shorter $$...$$ steps at logical equals signs; use intermediate variables if needed.
4. Inside math, use Wrytely-safe LaTeX. Preferred structures and symbols include: \frac{a}{b}, \sqrt{x}, x^2, x_i, \pm, \times, \div, \cdot, \le, \ge, \neq, \approx, \propto, \infty, \sum, \prod, \int, \pi, \theta, \sigma, \mu, \lambda, \omega, \vec{x}, \hat{x}, and \bar{x}.
5. Use \left(...\right) or \left[...\right] only when scalable grouping is needed.
6. For a piecewise result, you may use one \begin{cases}...\end{cases} block with two to four simple rows. Do not use any other LaTeX environment.
7. Do not use \(...\), \[...\], HTML, matrix, pmatrix, bmatrix, aligned, align, equation, gather, split, overbrace, or underbrace.
8. Do not put explanatory words inside math delimiters. Put them before or after the equation as plain text.
9. Never use presentation or font commands: \mathbf, \boldsymbol, \mathbb, \mathcal, \mathsf, \mathtt, \mathit, \text, \mathrm, or \operatorname. If the source uses a bold vector such as \mathbf{E}, rewrite it as \vec{E}. If bold is only emphasis, remove the bold command and keep its contents.
10. Never use a mathematical answer box: do not use \boxed, \fbox, \colorbox, or \color. The required outer plain-text code block is only a copyable delivery container; it must not contain a boxed equation.
11. Replace \overline{x} with \bar{x} and replace \overrightarrow{x} with \vec{x}.
12. Write units with ordinary letters, for example $5 m$ or $8.854 \times 10^{-12} F/m$.
13. Do not escape the math delimiters: write $ and $$ literally, never \$ or \$$.
14. COMPACT LAYOUT: do not insert empty lines anywhere inside the code block. Put each explanation or equation directly on the next line. Combine consecutive algebraic transformations into one equation with equals signs when they fit clearly, instead of creating many tiny equation blocks.
15. Preserve every necessary calculation and the final result accurately, but remove repeated givens, repeated conclusions, decorative wording, and unnecessary intermediate lines.
16. Explanation level: Use at most one short plain-text sentence for each major calculation. Do not add headings, step numbers, repeated givens, summaries, or a separate final-answer label.

Before sending, silently verify that your response contains exactly one plain-text code block, that every part of the solution is inside it, and that nothing appears outside it.