chore: removing ACP and fixing links (#335)

* chore: removing acp mentions

Signed-off-by: Aron Kerekes <arkereke@cisco.com>

* fix: updating broken link

Signed-off-by: Aron Kerekes <arkereke@cisco.com>

---------

Signed-off-by: Aron Kerekes <arkereke@cisco.com>

Author: keraron

docs/dir/directory-sandbox-deployment.md

@@ -154,7 +154,7 @@ For production deployment, consider these enhancements:
 
 - Use ExternalSecrets Operator with Vault instead of hardcoded secrets.
 - See commented ExternalSecrets configuration in values.yaml.
-- Reference: [agntcy-deployment](https://github.com/agntcy/agntcy-deployment) repository for production patterns.
+- RefFor more information, see the [ExternalSecrets configuration](https://github.com/agntcy/dir/blob/4bac23d129f030736198bf25708c24db97fc4547/install/charts/dir/values.yaml#L341-L382).
 
 **Resource Sizing**:
 

docs/identity/flow.md

@@ -63,7 +63,7 @@ This sequence diagram illustrates the process of creating, publishing, and regis
 sequenceDiagram
 autonumber
 
-Agent Creator->>e.g. Github: Publish agent source<br/>code and ACP manifest
+Agent Creator->>e.g. Github: Publish agent source<br/>code
 
 Agent Creator->>Identity CLI: Create and publish ResolverMetadata with an Agent ID
 
@@ -82,7 +82,7 @@ This sequence diagram illustrates the process of updating an existing Agent alon
 sequenceDiagram
 autonumber
 
-Agent Creator->>e.g. Github: Update and publish agent source<br/>code and ACP manifest
+Agent Creator->>e.g. Github: Update and publish agent source<br/>code
 
 Agent Creator->>Directory CLI: Update Agent OASF keeping the same<br/>Agent ID in identity extension
 
@@ -135,7 +135,7 @@ Agent Consumer->>Identity CLI: Verify the Agent Badge
 sequenceDiagram
 autonumber
 
-Agent Creator->>e.g. Github: Publish agent source<br/>code and ACP manifest
+Agent Creator->>e.g. Github: Publish agent source<br/>code
 activate e.g. Github
 e.g. Github-->>Agent Creator: Published
 deactivate e.g. Github
@@ -192,7 +192,7 @@ deactivate Identity CLI
 sequenceDiagram
 autonumber
 
-Agent Creator->>e.g. Github: Update and publish agent source<br/>code and ACP manifest
+Agent Creator->>e.g. Github: Update and publish agent source<br/>code
 activate e.g. Github
 e.g. Github-->>Agent Creator: Published
 deactivate e.g. Github

docs/index.md

@@ -38,7 +38,7 @@ The initial set of IoA components and architecture is outlined below. This is a
 ![IoA Stack](assets/ioa_stack.png)
 
 1. **[Open Agent Schema Framework (OASF)](./oasf/open-agentic-schema-framework.md)**: An OCI based extensible data model allowing to describe agents' attributes and ensuring unique identification of agents. OASF supports the description of A2A agents, MCP servers and can be extended to support other popular formats, such as Copilot agent manifests and many more. Current OASF repo can be found [here](https://github.com/agntcy/oasf), OASF schema documentation can be found [here](https://schema.oasf.outshift.com).
-1. **[Agent Directory](./dir/overview.md)**: Allows announcing and discover agents or multi-agent applications which are described using OASF. Any organization can run its directory and keep it in sync with others, forming the Internet of Agents inventory. Agent Directory supports A2A agent cards, ACP agent manifests, and MCP server descriptions among other data models.
+1. **[Agent Directory](./dir/overview.md)**: Allows announcing and discover agents or multi-agent applications which are described using OASF. Any organization can run its directory and keep it in sync with others, forming the Internet of Agents inventory. Agent Directory supports A2A agent cards and MCP server descriptions among other data models.
 1. **[Messaging SDK](./messaging/slim-core.md)**:
       * **SLIM** (Secure Low-latency Interactive Messaging): A protocol that defines the standards and guidelines for secure and efficient network-level communication between AI agents. SLIM ensures interoperability and seamless data exchange by specifying message formats, transport mechanisms, and interaction patterns.
       * **SLIM Nodes and SDK**: Offers handy secure (MLS and quantum safe) network-level communication services to a group of agents (typically those of a given multi-agent application) through SDK/Libraries. It extends gRPC to support pub/sub interactions in addition to request/reply, streaming, fire & forget and more.