Use the full project name in prose

Author: skydoves

CHANGELOG.md

@@ -1,4 +1,4 @@
-# compose-nav-graph - Changelog
+# Compose Navigation Graph - Changelog
 
 All notable changes to this project will be documented in this file.
 

README.md

@@ -255,7 +255,7 @@ The full guide, including multi module baselines and CI integration, lives in th
 
 ## Kotlin Multiplatform Support
 
-compose-nav-graph works on **Kotlin Multiplatform** out of the box: the annotations live in `commonMain` (published
+Compose Navigation Graph works on **Kotlin Multiplatform** out of the box: the annotations live in `commonMain` (published
 for `android`, `jvm`, `iosArm64`/`iosSimulatorArm64`/`iosX64`, `js`, and `wasmJs`), and the Gradle plugin detects your
 module shape and wires the right KSP pass automatically:
 

docs/gradle-plugin/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-The compose-nav-graph Gradle plugin (`com.github.skydoves.navgraph`) wires the whole toolkit into your build. When applied, it adds the `compose-nav-graph-annotations` and `compose-nav-graph-ksp` dependencies, registers the KSP processor that statically extracts your nav graph, sets up device free thumbnail rendering, and registers the nav tasks (`generateNavGraph`, `navDump` / `navCheck`, the HTML and PNG exports, and the preview gallery). It supports Kotlin Multiplatform and multi module projects.
+The Compose Navigation Graph Gradle plugin (`com.github.skydoves.navgraph`) wires the whole toolkit into your build. When applied, it adds the `compose-nav-graph-annotations` and `compose-nav-graph-ksp` dependencies, registers the KSP processor that statically extracts your nav graph, sets up device free thumbnail rendering, and registers the nav tasks (`generateNavGraph`, `navDump` / `navCheck`, the HTML and PNG exports, and the preview gallery). It supports Kotlin Multiplatform and multi module projects.
 
 The toolkit is not tied to Navigation 3. **Navigation 3 `NavKey` destinations are picked up automatically**, and any other class wires in through the annotations: Navigation 2 routes, or even plain Activities referenced by `@NavEdge` or `@NavPreview`, become nodes without implementing `NavKey`. An existing app lights up without refactoring.
 

docs/kotlin-multiplatform.md

@@ -1,6 +1,6 @@
 # Kotlin Multiplatform
 
-compose-nav-graph supports **Kotlin Multiplatform** out of the box. The annotations are a KMP library that lives in
+Compose Navigation Graph supports **Kotlin Multiplatform** out of the box. The annotations are a KMP library that lives in
 your `commonMain` source set (published for `android`, `jvm`, `iosArm64` / `iosSimulatorArm64` / `iosX64`, `js`, and
 `wasmJs`), and the Gradle plugin detects your module's shape and wires the right KSP pass for you. There is no
 KMP specific configuration: you apply the same two plugins as on a plain Android module.