<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Quality on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/quality/</link>
    <description>Recent content in Quality on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/quality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LanguageTool vs Vale vs textlint: Self-Hosted Grammar and Style Checking Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-29-languagetool-vs-vale-vs-textlint-self-hosted-grammar-style-checking-guide-2026/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-29-languagetool-vs-vale-vs-textlint-self-hosted-grammar-style-checking-guide-2026/</guid>
      <description>&lt;p&gt;Writing clear, error-free documentation at scale is one of the hardest problems for engineering teams. Relying on cloud-based grammar checkers like Grammarly means sending your internal documents — API specs, runbooks, architecture decision records — through third-party servers. For teams with compliance requirements or privacy concerns, self-hosted grammar and style checking is not optional.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
