QPSG blog — who uses this language & how we help

Real workflows from natural-person filings, pro se court work, trusts, affidavits, and contracts. Each article maps common language problems to what the processor checks and corrects.

New

Read a claim forward, then backward

Three certification samples: the swap of the first and last lodial-fact pair, the pair notes, and the line that does not certify.

Read article →
New

One court line, and the 15 October rules

IT, HEREBY, SHALL, lodials versus pronouns, phrase targets, name-form, and the limit of a structure score.

Read article →

Common trusts — benefits and limits

Revocable, irrevocable, spendthrift, special-needs, charitable, testamentary, and pour-over — what each form gives and where it fails.

Read article →

Pay with card or crypto

Card via Stripe. Crypto via NOWPayments. Same $18 / $50 plans. Activation is automatic after payment.

Read article →

QPSG value scale (~0~–~9~)

What the number under each word means after ANALYZE — a plain-language map for new authors.

Read article →

Word export → processor → copy back

Keep line breaks when you paste from Word, run QPSG, and paste back with Keep Text Only.

Read article →

Living wills and advance directives

Medical facts vs wishes — named declarant, condition, directive, and health-care agent. Not medical advice.

Read article →

Pour-over wills and trust coordination

Two documents, one fact set — same names, trust title, and date on the will and the trust.

Read article →

Homophones in legal drafts

Their/there, its/it is, affect/effect — the HOMOPHONES filter flags the pair; you pick the fact word.

Read article →

Free trial vs subscriber limits

Five free tests show the flags. Educational copies practice text. Operational files long documents with FULL-DOC.

Read article →

Loading templates without corrupting boilerplate

LOAD-TEMPLATE, the status panel, and how to keep the divine-law line intact — fill brackets, do not rewrite the catalog.

Read article →

Clerk notices & record demands

Please-be-advised language vs a present-tense notice to the clerk — what the processor flags before you send the page.

Read article →

Before/after: one complaint paragraph

Concrete tense, legalese, and pronoun cleanup on a single civil allegation — what the processor flags line by line.

Read article →

CSSCPSGP rules & procedures — Learn reference

Punctuation closures, P-L-F phrases, operational math ~0~–~9~, sentence template ~1~–~5~, and lexicon links — added to Learn QPSG.

Read article →

Who writes in Quantum Parse Syntax Grammar?

Overview of the people and communities that adopt QPSG — and the document problems they share.

Read article →

Natural persons & common-law style documents

Filings, notices, and records where the author speaks as a natural person — not a corporate fiction.

Read article →

Pro se litigants cleaning court language

Complaints, answers, and motions: cutting future tense and legalese before the clerk sees your PDF.

Read article →

Trust & estate authors without legalese drift

Trust creators and estate planners keeping gifts, appointments, and schedules in present-tense facts.

Read article →

Affidavits & declarations that state facts

Penalty-of-perjury blocks, unsworn declarations, and witness statements — one fact per line.

Read article →

Contracts in present-tense fact form

Private agreements, notes, and commercial language — clarity without changing your underlying deal.

Read article →

Seven language issues QPSG fixes (with examples)

Future tense, passive voice, pronouns, homophones, nominalizations — what the analyzer flags and why.

Read article →

Start with your document type

Prefer a use-case landing page? Browse trusts, wills, filings, and more — then open the processor with the right template category.

All landing pages → · Learn QPSG principles →