diff --git a/md/proxying-acp.md b/md/proxying-acp.md index 9e6319b..020bbea 100644 --- a/md/proxying-acp.md +++ b/md/proxying-acp.md @@ -19,7 +19,7 @@ Key changes: > How do things work today and what problems does this cause? Why would we change things? -Today's AI agent ecosystem is dominated by monolithic agents. We want people to be able to combine independent components to build custom agents targeting their specific needs. We want them to be able to use these with whatever editors and tooling they have. This is aligned with Symposium's core values of openness, interoperability, and extensibility. +Today's AI agent ecosystem is dominated by monolithic agents. We want people to be able to combine independent components to build custom agents targeting their specific needs. We want them to be able to use these with whatever editors and tooling they have. This is aligned with ACP's core values of openness, interoperability, and extensibility. # Motivating Example: Sparkle Integration diff --git a/src/agent-client-protocol-conductor/src/conductor.rs b/src/agent-client-protocol-conductor/src/conductor.rs index 4bc2557..25ae367 100644 --- a/src/agent-client-protocol-conductor/src/conductor.rs +++ b/src/agent-client-protocol-conductor/src/conductor.rs @@ -1,4 +1,4 @@ -//! # Conductor: SACP Proxy Chain Orchestrator +//! # Conductor: ACP Proxy Chain Orchestrator //! //! This module implements the Conductor conductor, which orchestrates a chain of //! proxy components that sit between an editor and an agent, transforming the diff --git a/src/agent-client-protocol-trace-viewer/src/viewer.html b/src/agent-client-protocol-trace-viewer/src/viewer.html index 206cd55..591e876 100644 --- a/src/agent-client-protocol-trace-viewer/src/viewer.html +++ b/src/agent-client-protocol-trace-viewer/src/viewer.html @@ -3,7 +3,7 @@ - SACP Trace Viewer + ACP Trace Viewer