diff --git a/content/en/cloud/workspaces/_index.md b/content/en/cloud/workspaces/_index.md
index 50e2c83d..0c096485 100644
--- a/content/en/cloud/workspaces/_index.md
+++ b/content/en/cloud/workspaces/_index.md
@@ -27,6 +27,10 @@ Workspaces facilitate collaboration between you and your teams, allow you to con
 
 - Access to Workspaces may be granted to one or more teams.
 - As a point of collaboration to facilitate work, Workspaces may have zero or more Environments associated.
+- A Workspace is closely associated with Teams in Meshery. Teams are groups of users with varying permissions, and they are at the center of resource access and management within a Workspace.
+- One ore more teams can be assigned to a workspace.
+- Same team can be assigned to multiple workspaces.
+- A team can be assigned to a workspace only if the team is not already assigned to another workspace.
 
 After creating a Workspace, of your next steps is to resource that Workspace. Like a shared drive (or or shared collection of files). Workspaces are your Google Drive, while Meshery Designs are your Google Docs.
 
diff --git a/content/en/meshmap/getting-started/creating-relationships.md b/content/en/meshmap/getting-started/creating-relationships.md
index da23be1a..39cebf83 100644
--- a/content/en/meshmap/getting-started/creating-relationships.md
+++ b/content/en/meshmap/getting-started/creating-relationships.md
@@ -12,7 +12,6 @@ tags: [designs]
 Page under construction.
 {{% /pageinfo %}}
 
-
 <!-- Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).
 
 There should be whitespace between paragraphs. Vape migas chillwave sriracha poutine try-hard distillery. Tattooed shabby chic small batch, pabst art party heirloom letterpress air plant pop-up. Sustainable chia skateboard art party banjo cardigan normcore affogato vexillologist quinoa meggings man bun master cleanse shoreditch readymade. Yuccie prism four dollar toast tbh cardigan iPhone, tumblr listicle live-edge VHS. Pug lyft normcore hot chicken biodiesel, actually keffiyeh thundercats photo booth pour-over twee fam food truck microdosing banh mi. Vice activated charcoal raclette unicorn live-edge post-ironic. Heirloom vexillologist coloring book, beard deep v letterpress echo park humblebrag tilde.
diff --git a/content/en/meshmap/tasks/_index.md b/content/en/meshmap/tasks/_index.md
index 2ff99d1d..3c4da65d 100755
--- a/content/en/meshmap/tasks/_index.md
+++ b/content/en/meshmap/tasks/_index.md
@@ -1,6 +1,6 @@
 ---
 title: Core Tasks
-description: What can your user do with your project?
+description: Navigate your way around MeshMap with these common tasks.
 date: 2023-10-30
 weight: 6
 ---
@@ -9,7 +9,7 @@ weight: 6
 Page under construction.
 {{% /pageinfo %}}
 
-Think about your project’s features and use cases. Use these to choose your core tasks. Each granular use case (enable x, configure y) should have a corresponding tasks page or tasks page section. Users should be able to quickly refer to your core tasks when they need to find out how to do one specific thing, rather than having to look for the instructions in a bigger tutorial or example. Think of your tasks pages as a cookbook with different procedures your users can combine to create something more substantial.
+<!-- Think about your project’s features and use cases. Use these to choose your core tasks. Each granular use case (enable x, configure y) should have a corresponding tasks page or tasks page section. Users should be able to quickly refer to your core tasks when they need to find out how to do one specific thing, rather than having to look for the instructions in a bigger tutorial or example. Think of your tasks pages as a cookbook with different procedures your users can combine to create something more substantial.
 
 You can give each task a page, or you can group related tasks together in a page, such as tasks related to a particular feature. As well as grouping related tasks in single pages, you can also group task pages in nested folders with an index page as an overview, as seen in this example site. Or if you have a small docset like the [Docsy User Guide](https://docsy.dev/docs/) with no Tutorials or Concepts pages, consider adding your feature-specific pages at the top level of your docs rather than in a Tasks section.
 
@@ -18,4 +18,4 @@ Each task should give the user
 * The prerequisites for this task, if any (this can be specified at the top of a multi-task page if they're the same for all the page's tasks. "All these tasks assume that you understand....and that you have already....").
 * What this task accomplishes.
 * Instructions for the task. If it involves editing a file, running a command, or writing code, provide code-formatted example snippets to show the user what to do! If there are multiple steps, provide them as a numbered list.
-* If appropriate, links to related concept, tutorial, or example pages.
+* If appropriate, links to related concept, tutorial, or example pages. -->
diff --git a/content/en/meshmap/tasks/designs/_index.md b/content/en/meshmap/tasks/designs/_index.md
index 91e74df9..0714a007 100755
--- a/content/en/meshmap/tasks/designs/_index.md
+++ b/content/en/meshmap/tasks/designs/_index.md
@@ -1,11 +1,10 @@
 ---
 title: Deploying Designs
 description: >
-  A short lead description about this section page. Text here can also be **bold** or _italic_ and can even be split over multiple paragraphs.
+  Each Meshery design is deployable to one or more Kubernetes clusters.
 date: 2023-10-30
 ---
 
 {{% pageinfo %}}
 Page under construction.
 {{% /pageinfo %}}
-
diff --git a/content/en/meshmap/tasks/designs/cloning-a-design.md b/content/en/meshmap/tasks/designs/cloning-a-design.md
index 653c6ab1..d5d6325e 100644
--- a/content/en/meshmap/tasks/designs/cloning-a-design.md
+++ b/content/en/meshmap/tasks/designs/cloning-a-design.md
@@ -1,7 +1,7 @@
 ---
 title: Cloning a Design
 description: >
-  A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
+  Treat designs as templates by cloning an existing design to modify and build upon.
 date: 2023-10-30
 weight: 5
 categories: [Designer]
@@ -12,7 +12,6 @@ tags: [designs]
 Page under construction.
 {{% /pageinfo %}}
 
-
 <!-- Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).
 
 There should be whitespace between paragraphs. Vape migas chillwave sriracha poutine try-hard distillery. Tattooed shabby chic small batch, pabst art party heirloom letterpress air plant pop-up. Sustainable chia skateboard art party banjo cardigan normcore affogato vexillologist quinoa meggings man bun master cleanse shoreditch readymade. Yuccie prism four dollar toast tbh cardigan iPhone, tumblr listicle live-edge VHS. Pug lyft normcore hot chicken biodiesel, actually keffiyeh thundercats photo booth pour-over twee fam food truck microdosing banh mi. Vice activated charcoal raclette unicorn live-edge post-ironic. Heirloom vexillologist coloring book, beard deep v letterpress echo park humblebrag tilde.
diff --git a/content/en/meshmap/tasks/designs/deploying-designs.md b/content/en/meshmap/tasks/designs/deploying-designs.md
index a46d27ea..33157534 100644
--- a/content/en/meshmap/tasks/designs/deploying-designs.md
+++ b/content/en/meshmap/tasks/designs/deploying-designs.md
@@ -1,7 +1,7 @@
 ---
 title: Deploying Designs
 description: >
-  A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
+    Each Meshery design is deployable to one or more Kubernetes clusters.
 date: 2023-10-30
 weight: 4
 categories: [Designer]
diff --git a/content/en/meshmap/tasks/designs/undeploying-designs.md b/content/en/meshmap/tasks/designs/undeploying-designs.md
index d1117a2a..0157678d 100644
--- a/content/en/meshmap/tasks/designs/undeploying-designs.md
+++ b/content/en/meshmap/tasks/designs/undeploying-designs.md
@@ -1,7 +1,7 @@
 ---
 title: Undeploying Designs
 description: >
-  A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
+  Undeploy a design in order to rollback a deployment from one or more Kubernetes clusters.
 date: 2023-10-30
 weight: 3
 categories: [Designer]
diff --git a/content/en/meshmap/tasks/designs/validating-designs.md b/content/en/meshmap/tasks/designs/validating-designs.md
index 82f5dac1..8c411016 100644
--- a/content/en/meshmap/tasks/designs/validating-designs.md
+++ b/content/en/meshmap/tasks/designs/validating-designs.md
@@ -1,7 +1,7 @@
 ---
 title: Validating Designs
 description: >
-  A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
+  Prior to deploying a design, you can validate the configuration that it contains in accordance with the target platform.
 date: 2023-10-30
 weight: 2
 categories: [Designer]