Technical writing
Markdown Math with KaTeX
Last updated: July 26, 2026
Math support helps with study notes, engineering docs, product analysis, and research drafts. VeloWrite renders math with KaTeX in the preview, so formulas can stay beside the plain text that explains them.
Use inline math for small expressions
Inline math belongs inside a sentence, where the expression is short enough not to interrupt reading. Use it for variables, units, compact equations, and short references that need to stay close to the surrounding words.
If the expression needs its own explanation, do not force it inline. Put it in a block and use the paragraph before or after the formula to explain what the reader should notice.
The term $x_i$ represents one input sample, and $n$ is the total number of samples.
A simple average can be written as $\bar{x}$ when the full equation is explained nearby.Inline math is best when it supports the sentence instead of replacing it.
Use block math when the formula is the point
Block math should stand on its own. It is better for equations that readers need to inspect, copy, compare, or discuss in a review.
A good pattern is simple: introduce the idea, show the formula, then explain the variables. The document stays readable even for someone scanning before reading closely.
The arithmetic mean is the sum of all samples divided by the sample count:
$\bar{x} = \frac{1}{n}\sum_{i=1}^{n}x_i$
Here, $x_i$ is one sample and $n$ is the total number of samples.Preview the rendered result before sharing technical documents.
Keep surrounding explanation clear
A formula without context is hard to use. Explain what each variable means, then show the equation, then describe how it affects the document's conclusion.
Do not assume future readers will remember why a symbol was chosen. In team docs, study notes, and product analysis, a small variable list can save time later.
We use a weighted score when recent signals matter more than older ones:
$S = \sum_{i=1}^{n} w_i x_i$
| Symbol | Meaning |
| --- | --- |
| $S$ | Final score |
| $w_i$ | Weight for signal $i$ |
| $x_i$ | Signal value |A short table helps when symbols appear more than once.
Use tables for small math references
Tables fit compact reference material: symbol definitions, parameter ranges, model assumptions, or before-and-after values. Keep cells short so the Markdown source remains readable.
If a formula, explanation, or derivation becomes long, move it out of the table and into a normal section. Long math inside table cells is hard to edit and easy to break.
| Term | Meaning | Example |
| --- | --- | --- |
| $r$ | Growth rate | $r = 0.08$ |
| $t$ | Time period | $t = 12$ months |
| $P_t$ | Projected value | $P_t = P_0(1+r)^t$ |Tables are for reference, not for long derivations.
Write math notes for rereading
The best math note is the one you can reopen later and understand quickly. Use headings for the problem, assumptions, formula, and conclusion.
For study notes, keep one concept per section. For engineering notes, include the decision that the formula supports. For product analysis, write the conclusion in words before the equation becomes too detailed.
## Conversion estimate
We estimate monthly paid users from traffic, activation, and paid conversion.
$P = V \times a \times c$
Where:
- $V$ is monthly visitors
- $a$ is editor activation rate
- $c$ is activated-to-paid conversion
If $V = 10,000$, $a = 0.15$, and $c = 0.03$, then $P = 45$ new paid users.The formula is easier to trust when the assumptions are visible.
Preview formulas before sharing
Math syntax is easy to mistype. A missing brace or an unclosed delimiter can make a clean note look broken. Split preview helps you catch those mistakes while the source is still visible.
In VeloWrite, use the web editor for quick math checks and the desktop app for local technical documents you will revise. Local files, recent documents, and history snapshots matter more once the note becomes part of a real project.
# Formula Check
## Source
The expected value is:
$E[X] = \sum_x x \cdot P(X=x)$
## Review
- Does the formula render?
- Are variables explained?
- Is the conclusion written in plain language?Preview is not decoration. It is part of reviewing a technical draft.