Skip to content

Handbook: fix article errors in Subscription Agreement 1.5 - #5731

Open
MichaelBDavis wants to merge 1 commit into
mainfrom
handbook-subscription-agreement-article-fix
Open

Handbook: fix article errors in Subscription Agreement 1.5#5731
MichaelBDavis wants to merge 1 commit into
mainfrom
handbook-subscription-agreement-article-fix

Conversation

@MichaelBDavis

Copy link
Copy Markdown
Contributor

Follow-up to #5729, which standardized quote naming and surfaced these errors.

What

subscription-agreement-1.5.md contains 12 instances of "an Quote" across 11 lines. The agreement was drafted with a defined term taking "an" and later globally replaced with "Quote", without correcting the articles.

Section 2 (Acceptance) also carries a doubled replacement:

(b) reference to an Quote Quote No. within a purchase order or similar document

Changes

  • an Quotea Quote — 11 instances, on lines 17 (×2), 75, 77, 79, 121, 175, 177, 201, 255
  • AN QUOTEA QUOTE — 1 instance, in the all-caps warranty disclaimer in 3.4 (line 105)
  • Line 27, Acceptance definition — removes the duplicated word so it reads reference to a Quote No.

Please review line 27 specifically

Every other edit is a bare article correction and mechanically safe. Line 27 is the one place a word is removed rather than corrected. The reading it produces matches how the number is used in practice — a customer citing the quote number on their PO, per the Company Quote Reference Number rule in Engagements & Pricing — but it is worth a deliberate look rather than being waved through with the articles.

Verification

Diffed word-by-word against main: line count unchanged, and every changed line differs only by ana (or ANA), except line 27's removed duplicate. No defined terms, obligations, amounts, or substantive wording touched.

Note on scope

This file is live customer-facing legal text — the header warns it is still referenced in contracts and quotes, and it is the document customers sign per the closing line of Appendix 1. It was deliberately kept out of #5729 so a wording change to an executed-contract template is not buried in a process-documentation PR. Per Legal, agreement changes route through Deal Desk — flagging that in case this needs that sign-off before merge, even though the change is grammatical.

🤖 Generated with Claude Code

The agreement was drafted with a defined term taking "an" and later
globally replaced with "Quote" without correcting the articles, leaving
12 instances of "an Quote" across 11 lines. Section 2 "Acceptance" also
carries a doubled replacement: "reference to an Quote Quote No."

Corrects the articles to "a Quote" (and "A QUOTE" in the all-caps
warranty disclaimer in 3.4), and removes the duplicated word in the
Acceptance definition so it reads "reference to a Quote No."

Grammar only. No defined terms, obligations, or substantive wording are
changed; every edit is an article correction except the one duplicated
word.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@netlify

netlify Bot commented Sep 2, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit 75c9fd8
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a9830a4f696ef0007344eca
😎 Deploy Preview https://deploy-preview-5731--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 74 (🟢 up 24 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 85 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@MichaelBDavis

Copy link
Copy Markdown
Contributor Author

@ZJvandeWeg I suspect we can ignore this is 1.6 is coming soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant