Merge pull request #45 from pubky/docs/standardize-pkarr-casing

Standardize PKARR casing (Pkarr → PKARR)

Author: gcomte

Explore/PubkyCore/Pkarr/1.WhyPkarr.md

@@ -1,5 +1,5 @@
 ---
-title: "Why Pkarr?"
+title: "Why PKARR?"
 aliases:
   - "../../Pubky-Core/Pkarr/1.Why-Pkarr"
 ---

Explore/PubkyCore/Pkarr/2.GettingStartedWithPkarr.md

@@ -1,5 +1,5 @@
 ---
-title: "Getting Started with Pkarr"
+title: "Getting Started with PKARR"
 aliases:
   - "../../Pubky-Core/Pkarr/2.Getting-Started-with-Pkarr"
 ---

Explore/PubkyCore/index.md

@@ -7,4 +7,4 @@ title: "Pubky Core"
 - [[Explore/PubkyCore/SDK|SDK]]
 - [[Explore/PubkyCore/Authentication|Authentication]]
 - [[Explore/PubkyCore/Homeserver|Homeserver]]
-- [[Explore/PubkyCore/Pkarr/0.Introduction|Pkarr]]
+- [[Explore/PubkyCore/Pkarr/0.Introduction|PKARR]]

Explore/Technologies/PubkyDocker.md

@@ -10,7 +10,7 @@ aliases:
 
 Pubky Docker orchestrates the following components:
 
-1. **Pkarr Relay** - DHT relay for public key-addressable records
+1. **PKARR Relay** - DHT relay for public key-addressable records
 2. **Pubky Homeserver** - Decentralized data storage instance
 3. **Pubky Nexus** - Social media indexer and aggregator
 4. **Pubky App** - Social media client frontend
@@ -96,7 +96,7 @@ pubky-workspace/
 
 ## Stack Components
 
-### 1. Pkarr Relay (Port 6882)
+### 1. PKARR Relay (Port 6882)
 Local DHT relay for public key-addressable resource records. Enables domain resolution for Pubky identities.
 
 **Configuration**: `pkarr.config.toml`
@@ -168,7 +168,7 @@ The stack uses a custom Docker bridge network (`172.18.0.0/16`) with static IPs:
 
 | Service | IP | External Ports |
 |---------|------|---------------|
-| Pkarr | 172.18.0.2 | 6882 |
+| PKARR | 172.18.0.2 | 6882 |
 | Nexus | 172.18.0.3 | 8080, 8081 |
 | Homeserver | 172.18.0.4 | 6286-6288, 15411-15412 |
 | Neo4j | 172.18.0.5 | 7474, 7687 |
@@ -251,7 +251,7 @@ All data is stored in the `.storage/` directory:
 
 ```
 .storage/
-├── pkarr/          # Pkarr relay cache
+├── pkarr/          # PKARR relay cache
 ├── postgres/       # Homeserver database
 ├── neo4j/          # Nexus graph data
 ├── redis/          # Nexus search index
@@ -324,7 +324,7 @@ The Pubky Docker stack demonstrates the full architecture of a Pubky Social appl
              └──────────┬───────────┘
                         │
                  ┌──────▼───────┐
-                 │ Pkarr Relay  │
+                 │ PKARR Relay  │
                  │ (DHT/DNS)    │
                  └──────────────┘
 ```

FAQ.md

@@ -68,7 +68,7 @@ Yes. You'll need port forwarding or tunneling if behind NAT.
 Use [[PubkyExplorer|Pubky Explorer]] ([explorer.pubky.app](https://explorer.pubky.app)), a web-based file browser for public Pubky data. Enter any public key or path (e.g., `pubky://your-key/pub/pubky.app/profile.json`) to browse files and directories stored on Homeservers. Features include keyboard navigation, file preview, directory traversal, and shareable URLs.
 
 **Q18. How can I run the complete Pubky stack locally for development?**  
-Use [[PubkyDocker|Pubky Docker]], a Docker Compose orchestration that runs the entire Pubky Social stack with one command. It includes Pkarr relay, Homeserver (with PostgreSQL), Pubky Nexus (with Neo4j and Redis), and the Pubky App frontend—all preconfigured and ready to use. Clone the repository, configure `.env` for testnet or mainnet, and run `docker compose up -d`. Perfect for testing integrations, developing custom frontends, or learning how all components interact. See [[PubkyDocker|Pubky Docker]] for setup instructions.
+Use [[PubkyDocker|Pubky Docker]], a Docker Compose orchestration that runs the entire Pubky Social stack with one command. It includes PKARR relay, Homeserver (with PostgreSQL), Pubky Nexus (with Neo4j and Redis), and the Pubky App frontend—all preconfigured and ready to use. Clone the repository, configure `.env` for testnet or mainnet, and run `docker compose up -d`. Perfect for testing integrations, developing custom frontends, or learning how all components interact. See [[PubkyDocker|Pubky Docker]] for setup instructions.
 
 **Q19. When should I use Pubky Docker vs SDK libraries?**  
 Use the SDK libraries ([@synonymdev/pubky](https://www.npmjs.com/package/@synonymdev/pubky) for JavaScript, [pubky](https://crates.io/crates/pubky) for Rust) when building applications that interact with Pubky. Only use [[PubkyDocker|Pubky Docker]] if you need to run the full stack locally to experiment with Pubky Nexus, test custom social frontends, debug cross-component issues, or learn the complete architecture. For most app development, the SDK libraries connected to public infrastructure are simpler and faster.