Workspace docs audit (#176)

Author: willemcdejongh

_snippets/create-aws-resources.mdx

@@ -23,7 +23,7 @@ This will create:
 5. [Secrets](https://aws.amazon.com/secrets-manager/) for managing application and database secrets.
 6. [RDS Database](https://aws.amazon.com/rds/) for Knowledge Base and Storage.
 
-**Press Enter** to confirm and grab a cup of coffee while the resources spin up.
+**Press Enter** to confirm and wait for the resources to spin up.
 
 - The RDS database takes about 5 minutes to activate.
 - These resources are defined in the `workspace/prd_resources.py` file.

_snippets/run-agent-api-and-database.mdx

@@ -1,6 +1,6 @@
 ## Serve your Agents using FastAPI
 
-[FastAPI](https://fastapi.tiangolo.com/) is an exceptional framework for building RestApis. Its fast, well-designed and loved by everyone using it. Most production applications are built using a front-end framework like [next.js](https://nextjs.org) backed by a RestAPI, where FastAPI shines.
+[FastAPI](https://fastapi.tiangolo.com/) is an exceptional framework for building REST APIs. Its fast, well-designed and loved by everyone using it. Most production applications are built using a front-end framework like [next.js](https://nextjs.org) backed by a REST API, where FastAPI shines.
 
 Your codebase comes pre-configured with [FastAPI](https://fastapi.tiangolo.com/) and [PostgreSQL](https://www.postgresql.org/), along with some sample routes. Start your workspace using:
 

_snippets/run-agent-app-local.mdx

@@ -35,4 +35,4 @@ Notes:
 
 - The `Agents` are defined in the `agents` folder.
 - The streamlit apps are defined in the `ui` folder
-- The api routes are defined in the `api` folder.
+- The API routes are defined in the `api` folder.

_snippets/setup.mdx

@@ -51,7 +51,7 @@
     </CodeGroup>
 
     <Tip>
-    Agno works with any model provider, just need to update the agents in the workspace.
+    Agno is compatible with any model provider; simply update the agents in the workspace.
     </Tip>
   </Step>
 </Steps>

workspaces/agent-app/local.mdx

@@ -9,7 +9,8 @@ The Agent App is our go-to workspace for building agentic systems. It contains:
 - A streamlit application for debugging and testing. This streamlit app is very versatile and can be used as an admin interface for the agentic system and shows all sorts of data.
 - A postgres database for session and vector storage.
 
-This Agentic System is designed to run locally using docker and in production on AWS.
+
+It's designed to run locally using docker and in production on AWS.
 
 <Snippet file="setup.mdx" />
 

workspaces/introduction.mdx

@@ -39,14 +39,11 @@ We recommend starting with the `agent-app` template and taking it from there.
 When building Agents, we experiment locally till we achieve 6/10 quality.
 This helps us see quick results and get a rough idea of how our solution should look like in production.
 
-Then, we start moving to a production environment and iterate from there. We create a new workspace and start connecting different parts of the system. This gives us a working solution that we can test and evaluate.
-
-Here's how we like to build agentic systems:
-
-- Serve Agents, Teams and Workflows via a RestAPI (FastAPI).
+Then, we start moving to a production environment and iterate from there. Here's how __*we*__ build production systems:
+- Serve Agents, Teams and Workflows via a REST API (FastAPI).
 - Use a streamlit application for debugging and testing. This streamlit app is generally used as an admin interface for the agentic system and shows all sorts of data.
-- Monitor, evaluate and improve till we reach 9/10 quality.
-- In parallel, we start integrating our front-end with the Rest API above.
+- Monitor, evaluate and improve the implementation until we reach 9/10 quality.
+- In parallel, we start integrating our front-end with the REST API above.
 
 Having built 100s of such systems, we have a standard set of codebases we use and we call them **Workspaces**. They help us manage our Agentic System as code.