Four Ways AI Polishing Can Accidentally Change a Paper's Meaning

BlogEasyLaTeXPublished

“Keep the original meaning” is not a precise enough polishing instruction. AI may not recognize which words encode a definition, a mathematical relationship, or the limits of a claim. Identify those boundaries before reviewing the result.

1. Protect Defined Terms and Symbols

A term often appears first as a definition and later as a deliberate repetition. A request to “make wording consistent” can accidentally merge or replace both uses.

Where appropriate, define stable terms and symbols as macros, and limit polishing to the surrounding narrative:

\documentclass[11pt]{article}
\usepackage{amsmath}
\usepackage{natbib}

% Define stable terms and symbols as macros
\newcommand{\gd}{gradient descent}
\newcommand{\lrate}{\eta}

\begin{document}

\section{Convergence}
\label{sec:conv}
In practice, \gd{} is usually run with a small \(\lrate\).
We observe that the loss decreases monotonically under
this schedule~\citep{bottou2012}. Equation~\eqref{eq:update}
is applied at every step.

\begin{equation}
  \theta_{t+1} = \theta_t - \lrate \nabla J(\theta_t)
  \label{eq:update}
\end{equation}

\begin{thebibliography}{9}
\bibitem[Bottou(2012)]{bottou2012}
Bottou L. Stochastic Gradient Descent Tricks. 2012.
\end{thebibliography}

\end{document}

A macro changes every use when its definition changes. Preserve intentional exceptions—for example, a full name in the abstract and an abbreviation in the body. Use project-wide search to inspect the definition and calls when needed.

2. Preserve Inline Math and Citation Commands

AI can change a learning-rate macro such as \lrate into \alpha, or change an index from t+1 to t. It may also replace \eqref{eq:update} with a hard-coded “Equation (1),” which becomes wrong after another equation is inserted.

Ask for sentence-by-sentence comparison:

Polish the prose in this section while preserving defined terms, formulas, cross-references, and qualifiers exactly. Return only changed sentences in a Before / After table. Keep inline math, \citep, \ref, \label, and related LaTeX structures intact; do not rewrite or omit them.

Then check:

  1. Symbols and commands inside inline math.
  2. Citation keys in \citep and \cite, including omissions or moved citations.
  3. Complete \ref and \eqref calls pointing to the original labels.

3. Watch for Lost Qualifiers and Stronger Claims

Removing “under these assumptions” or “typically” can make a sentence shorter while changing its scope.

  • Removing a frequency qualifier can turn a recurring observation into an apparent universal rule.
  • Shortening a conditional clause can erase the conditions under which a result holds.
  • Replacing “suggests” with “shows” or “proves” can make the claim stronger than the evidence.

These changes need not cause any compilation error. Inspect conclusion sentences and changes in verb strength especially carefully. Keep the original wording when the proposed version overstates the result.

4. Finish with Compilation and a Source Diff

Successful compilation does not establish that the scientific meaning is unchanged. Use two checks:

  1. Compile to detect broken macros, formulas, and references.
  2. Compare the source before and after with a diff or text comparison. Inspect mathematical notation, citation markers, defined terms, and qualifications line by line.

Takeaways

  • Separate ordinary prose from definitions and technical commitments before polishing.
  • Use macros for stable terminology where they improve clarity.
  • Request a Before / After comparison with intact LaTeX.
  • Manually review conditions, claim strength, and all technical notation.