fix(docs): fixes in Agentverse docs (#1024)

Co-authored-by: Joshua Croft <[email protected]>

pages/concepts/agent-services/_meta.json

@@ -4,7 +4,7 @@
     "timestamp": true
   },
   "agent-explorer": {
-    "title": "Agentverse: Explorer",
+    "title": "Agentverse: Marketplace",
     "timestamp": true
   },
   "agent-hosting": {

pages/concepts/agent-services/agent-explorer.mdx

@@ -1,18 +1,24 @@
 import { Callout } from 'nextra/components'
 
-# Agentverse: Explorer
+# Agentverse: Marketplace
 
-The **Agentverse Explorer** lets you look for and connect with other agents registered in the [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview). Agents being developed on the Agentverse are automatically registered in the Almanac, making it simple for anybody to find them and explore their features. In light of this, it is possible to describe the Agentverse Explorer's functionality as that of a **Almanac Explorer**, as it enables the retrieval of detailed information on any agent that is recorded inside the Almanac.
+The **Agentverse Marketplace** lets you look for and connect with other agents registered in the [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview). Agents being developed on the Agentverse are automatically registered in the Almanac, making it simple for anybody to find them and explore their features. In light of this, it is possible to describe the Agentverse Marketplace's functionality as that of an **Almanac Explorer**, as it enables the retrieval of detailed information on any agent that is recorded inside the Almanac.
 
     <Callout type="info" emoji="ℹ️">
       It may be possible that users may not be willing to share agents information but rather wanting to keep them private for any reason. This is achievable thanks to the possibility of **differentiating between public and private agents**. Checkout the following resource for further understanding on this topic: [Public and private agents ↗️](/concepts/agents/public-private-agents).
     </Callout>
 
 ## Different types of agents
 
-Every agent available and displayed on the Explorer can be a: **Hosted**, **Local**, or **Mailbox** agent.
+Every agent available and displayed on the Marketplace can be a: **Hosted**, **Local**, or **Mailbox** agent.
 
-**Hosted** agents are agents being developed on the [Agentverse: My Agents ↗️](/concepts/agent-services/agent-hosting) and correctly registered within the Almanac contract and whose registration is up-to-date, meaning that all provided information is up-to-date. In this case the agent is denoted by a green **Active** tag. On the other hand, a **Local** agent is one pointing towards a local endpoint. These local agents' utility is limited in real-world contexts, but these are very useful for testing purposes. Finally, **Mailbox** agents are those registered within the [Agentverse: Mailroom ↗️](/concepts/agent-services/agent-mail) and thus are being able to send and receive messages continuously. Agents which are not online are visible as **Offline** agents.
+**Hosted** agents are agents being developed on the [Agentverse: My Agents ↗️](/concepts/agent-services/agent-hosting) and correctly registered within the Almanac contract and whose registration is up-to-date, meaning that all provided information is up-to-date. In this case the agent is denoted by a green **Active** tag. On the other hand, a **Local** agent is one pointing towards a local endpoint. 
+
+Check out this [resource ↗️](/guides/agents/intermediate/agent-types) for a better understanding of local Agents. A local agent's utility is limited in real-world contexts, but such Agents are very useful for testing purposes. 
+
+Finally, **Mailbox** Agents are those registered within the [Agentverse: Mailroom ↗️](/concepts/agent-services/agent-mail) and thus are being able to send and receive messages continuously. 
+
+Agents which are not online are visible as **Offline** agents.
 
 ## Look for registered agents