← Back to Home

AiToWords Conversion Samples

These examples show the kinds of AI-generated Markdown that users most often need to deliver as editable Word documents. Use them as a checklist before exporting long reports, academic notes, or technical documentation.

1. Formula-Heavy Notes

## Gradient Descent
For a parameter vector $\theta$, the update rule is:

$$
\theta_{t+1} = \theta_t - \eta \nabla_\theta J(\theta)
$$

Check whether inline formulas and display formulas remain editable in Word.

Open the exported document in Word or WPS and click the equation to verify it is not plain text.
Review subscripts, Greek letters, and fractions because these are common failure points in manual copy-paste workflows.

2. Technical Code Blocks

```js
function convert(markdown) {
  return renderWordDocument(markdown, {
    preserveCodeBlocks: true,
    preserveHeadingStyle: true
  });
}
```

Confirm that code blocks keep monospace formatting and do not merge with normal paragraphs.
For documents with many code snippets, export a short section first before processing the full file.

3. Wide Markdown Tables

| Metric | Input | Export Check | Suggested Fix |
| --- | --- | --- | --- |
| Columns | 8+ columns | Check page width | Split the table if needed |
| Long text | Multiple sentences | Check wrapping | Shorten labels before export |

Wide tables may need manual column width adjustment after export.
For final delivery, avoid mixing very long paragraphs with many narrow columns.

4. Delivery Checklist

- [ ] Heading levels are correct
- [ ] Tables are readable
- [ ] Formulas render correctly
- [ ] Code blocks stay separated
- [ ] Sensitive content was reviewed before sharing

Use a checklist when turning AI output into a formal client, academic, or internal document.
If something looks wrong, see the known issues page before re-exporting.