update

Signed-off-by: Lee Calcote <lee.calcote@layer5.io>

Author: leecalcote

content/en/cloud/catalog/_index.md

@@ -9,26 +9,26 @@ description: >
 Public Catalog: https://meshery.layer5.io/catalog
 {{%/pageinfo%}}
 
-## Catalog Concepts
-
-The catalog envisions a web-based, public catalog to facilitate easy discovery and investment-free catalog perusal. Content is published at meshery.layer5.io/catalog, and one-click import of catalog content into Meshery Server is seamlessly integrated.
+The Cloud Catalog is a web-based, public catalog to facilitate easy discovery of existing designs. Designs thaat are published into the catalog caan be, but are not alwaays curated for known best praactices and patterns. Content is published at meshery.layer5.io/catalog, and one-click import of catalog content into Meshery Server is seamlessly integrated.
 
 ### Content Visibility
 
-- Public: View and edit rights for all users.
-- Private: Associated roles and/or keys can dictate permissions.
+Each item in the catalog comes with an associated level of visibility.
+
+- Published: View and clone permission for all users. View for all non-users.
+- Public: View and edit permissions for all users.
+- Private: View and edit permissions only for design owner.
 
 ### Content Types
 
-- User-produced content: e.g., Performance profiles, filters, patterns.
-- Provider-produced content: e.g., Profiles, filters, patterns.
 
-### Content Classes
+### Content Categories
 
-- Policies, Filters, Programs, Extensions.
+Catalog content is categorized in a number of ways:
+ 
+<!-- List design metadata and descriptions here -->
 
 ### Content Tags
 
 - Arbitrary strings for categorization.
 - Content Support Levels: "Official", "Partner", "Community".
-

content/en/meshmap/visualizer/_index.md

@@ -10,6 +10,9 @@ categories: [Visuzalizer]
 Discover and visualize your Kubernetes clusters and cloud native infrastructure.
 {{% /pageinfo %}}
 
+
+{{< figure src="images/log-stream-sequence-diagram.svg" link="images/log-stream-sequence-diagram.svg"  width="100%"  >}}
+
 <!-- For many projects, users may not need much information beyond the information in the [Overview](/docs/overview/), so this section is **optional**. However if there are areas where your users will need a more detailed understanding of a given term or feature in order to do anything useful with your project (or to not make mistakes when using it) put that information in this section. For example, you may want to add some conceptual pages if you have a large project with many components and a complex architecture.
 
 Remember to focus on what the user needs to know, not just what you think is interesting about your project! If they don’t need to understand your original design decisions to use or contribute to the project, don’t put them in, or include your design docs in your repo and link to them. Similarly, most users will probably need to know more about how features work when in use rather than how they are implemented. Consider a separate architecture page for more detailed implementation and system design information that potential project contributors can consult. -->