@@ -16,7 +16,7 @@ Source: Divio Documentation System (diataxis.fr)
 | **Reference** | Information | Encyclopedia | "X is defined as…" |
 | **Explanation** | Understanding | Essay / article | "The reason X works this way is…" |
 
-## How This Maps to croktile-tutorial
+## How This Maps to croqtile-tutorial
 
 | Directory | Type | Write It As |
 |-----------|------|-------------|
 
@@ -6,7 +6,7 @@ alwaysApply: false
 
 # GPU Documentation Patterns
 
-Sources: NVIDIA CUDA Programming Guide, AMD Composable Kernel docs, croktile-tutorial best practices
+Sources: NVIDIA CUDA Programming Guide, AMD Composable Kernel docs, croqtile-tutorial best practices
 
 ## Progressive Complexity
 
 
@@ -1,16 +1,16 @@
 ---
-name: croktile-chapter-rewrite
+name: croqtile-chapter-rewrite
 description: >-
-  Rewrites Croktile tutorial chapters (ch01–ch09) to match the storytelling,
+  Rewrites Croqtile tutorial chapters (ch01–ch09) to match the storytelling,
   figure, and structure standards established in ch02 and ch03. Use when
   rewriting, reviewing, or restructuring any tutorial chapter, or when the
   user mentions chapter quality, chapter structure, or tutorial consistency.
 ---
 
-# Croktile Tutorial Chapter Rewrite Standard
+# Croqtile Tutorial Chapter Rewrite Standard
 
 This skill encodes the writing and structural conventions that emerged from
-human-reviewed iterations of Chapters 2 and 3 of the Croktile tutorial.
+human-reviewed iterations of Chapters 2 and 3 of the Croqtile tutorial.
 Apply these rules when rewriting or reviewing any tutorial chapter.
 
 ## 1. Opening Pattern (Mandatory)
@@ -34,22 +34,22 @@ The bridge is a single narrative sentence or short paragraph — not a bullet li
 
 ### Beat 2 — Concept Introduction (Storytelling)
 
-Before showing any Croktile syntax, explain the **concept itself** using
+Before showing any Croqtile syntax, explain the **concept itself** using
 general knowledge the reader can relate to:
 
 - What is this concept/model/mindset in the real world or in GPU hardware?
 - How do traditional tools (CUDA, OpenCL) handle it, and what makes it hard?
-- What is Croktile's key insight or design choice for this concept?
+- What is Croqtile's key insight or design choice for this concept?
 
 This section reads like a mini-essay — conversational, specific, opinionated.
 Avoid bullet-point walls. Use analogies, contrasts, and concrete numbers.
 
 > **Pattern** (ch02): "A GPU does not fetch one 32-bit integer from memory at a
 > time. It fetches contiguous blocks — 128 bytes, 256 bytes — in a single
-> transaction… Croktile is designed around this insight."
+> transaction… Croqtile is designed around this insight."
 
 > **Pattern** (ch03): "Parallelism is a virtual concept… CUDA conflates logical
-> structure and physical mapping… Croktile untangles them."
+> structure and physical mapping… Croqtile untangles them."
 
 ## 2. Single Storyline per Chapter
 
 
@@ -1,21 +1,21 @@
-# Croktile
+# Croqtile
 
-Documentation and tutorials for **Croktile**, a C++ embedded DSL for high-performance kernel programming, featuring easy-to-use syntax with zero-cost abstractions, comprehensive compile-time safety checks, first-class dynamic shapes and symbolic dimensions, and an AI-tuning-friendly design from the ground up.
+Documentation and tutorials for **Croqtile**, a C++ embedded DSL for high-performance kernel programming, featuring easy-to-use syntax with zero-cost abstractions, comprehensive compile-time safety checks, first-class dynamic shapes and symbolic dimensions, and an AI-tuning-friendly design from the ground up.
 
 ## Documentation Structure
 
 ### Part I — [Tutorial](tutorial/index.md)
 
-A step-by-step walkthrough for newcomers. Starts with the simplest possible kernel and progressively introduces Croktile syntax through increasingly sophisticated matmul variants. No prior Croktile experience required — just basic C++ and GPU programming concepts.
+A step-by-step walkthrough for newcomers. Starts with the simplest possible kernel and progressively introduces Croqtile syntax through increasingly sophisticated matmul variants. No prior Croqtile experience required — just basic C++ and GPU programming concepts.
 
 ### Part II — [Performance Tuning Demos](optimization/index.md)
 
 Case-oriented performance engineering. Each section profiles a real kernel family, identifies bottlenecks, and applies optimization patterns to push toward hardware peak. Covers profiling, benchmarking, compiler flags, and AI-tuning workflows.
 
 ### Part III — [Coding Reference](documentation/index.md)
 
-Exhaustive syntax and semantics reference. Every Croktile construct — shapes, DMA, loops, parallelism, events, memory, macros, and more — is documented in detail.
+Exhaustive syntax and semantics reference. Every Croqtile construct — shapes, DMA, loops, parallelism, events, memory, macros, and more — is documented in detail.
 
 ### Part IV — [Design Rationales](advanced/index.md)
 
-Deep-dive articles on Croktile's design rationale, tradeoffs, and frontier challenges. *(Planned)*
+Deep-dive articles on Croqtile's design rationale, tradeoffs, and frontier challenges. *(Planned)*
@@ -2,7 +2,7 @@
 
 *This section is planned for future content.*
 
-Deep-dive articles on Croktile's design rationale, tradeoffs, and frontier challenges — similar in spirit to the MLIR rationale documents.
+Deep-dive articles on Croqtile's design rationale, tradeoffs, and frontier challenges — similar in spirit to the MLIR rationale documents.
 
 ## Planned Topics