Skip to content

High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.

docs: clean up titles and remove redundant text

Boschc39e4072612f
diff --git a/cmd/pinchtab/cmd_bridge.go b/cmd/pinchtab/cmd_bridge.go
index f6e56598..6ace4884 100644
--- a/cmd/pinchtab/cmd_bridge.go
+++ b/cmd/pinchtab/cmd_bridge.go
@@ -16,11 +16,11 @@ import (
"github.com/pinchtab/pinchtab/internal/handlers"
)
-// runBridgeServer starts a bridge server without orchestrator or dashboard
+// runBridgeServer starts a bridge without orchestrator or dashboard
// This is used for spawned instances by the orchestrator
func runBridgeServer(cfg *config.RuntimeConfig) {
listenAddr := cfg.ListenAddr()
- slog.Info("🦀 Pinchtab Bridge Server", "listen", listenAddr, "profile", cfg.ProfileDir)
+ slog.Info("🦀 Pinchtab Bridge", "listen", listenAddr, "profile", cfg.ProfileDir)
// Create a bridge instance with lazy initialization
// Chrome will be initialized on first request via ensureChrome()
@@ -34,7 +34,7 @@ func runBridgeServer(cfg *config.RuntimeConfig) {
shutdownOnce := &sync.Once{}
doShutdown := func() {
shutdownOnce.Do(func() {
- slog.Info("shutting down bridge server...")
+ slog.Info("shutting down bridge...")
})
}
h.RegisterRoutes(mux, doShutdown)
@@ -53,7 +53,7 @@ func runBridgeServer(cfg *config.RuntimeConfig) {
}
go func() {
- slog.Info("bridge server listening", "addr", listenAddr)
+ slog.Info("bridge listening", "addr", listenAddr)
if err := server.ListenAndServe(); err != nil && err != http.ErrServerClosed {
slog.Error("server error", "err", err)
os.Exit(1)
diff --git a/docs/architecture/system-charts.md b/docs/architecture/system-charts.md
index 6fef3da8..387b4ff8 100644
--- a/docs/architecture/system-charts.md
+++ b/docs/architecture/system-charts.md
@@ -96,12 +96,3 @@ Important details:
- tab-scoped routes are resolved to the owning instance before execution
- the scheduler is optional, server-only, and applies to `/tasks`
- bridge handlers perform the actual browser work
-
-## Reading Guide
-
-Use the charts like this:
-
-- **Chart 1** for the product shape
-- **Chart 2** for onboarding and default usage
-- **Chart 3** for the difference between server mode and bridge mode
-- **Chart 4** for the current execution path
diff --git a/docs/guides/attach-chrome.md b/docs/guides/attach-chrome.md
index 95ef3a66..6669cfc0 100644
--- a/docs/guides/attach-chrome.md
+++ b/docs/guides/attach-chrome.md
@@ -1,4 +1,4 @@
-# Attach An Existing Chrome
+# Attach Chrome
Use this guide when:
diff --git a/docs/guides/raspberry-pi.md b/docs/guides/raspberry-pi.md
index a45d8d23..9284a032 100644
--- a/docs/guides/raspberry-pi.md
+++ b/docs/guides/raspberry-pi.md
@@ -1,4 +1,4 @@
-# Raspberry Pi Setup Guide
+# Raspberry Pi
PinchTab runs on Raspberry Pi as long as Chromium or Chrome is available. The current implementation does not need Pi-specific feature flags, but it does benefit from conservative defaults because memory is limited.
diff --git a/docs/implementations/managed-bridge-vs-managed-direct-cdp.md b/docs/implementations/managed-bridge-vs-managed-direct-cdp.md
index f70816db..d4d1f9c5 100644
--- a/docs/implementations/managed-bridge-vs-managed-direct-cdp.md
+++ b/docs/implementations/managed-bridge-vs-managed-direct-cdp.md
@@ -1,4 +1,4 @@
-# Managed Bridge vs Managed Direct-CDP
+# Bridge vs Direct-CDP
This page compares two ways Pinchtab can manage a browser instance:
diff --git a/docs/reference/index.md b/docs/reference/index.md
index bf5d9db2..9df70c32 100644
--- a/docs/reference/index.md
+++ b/docs/reference/index.md
@@ -1,4 +1,4 @@
-# CLI Reference
+# Reference
Reference pages for the current PinchTab CLI and closely related command-facing endpoints.