More

Author: mjang

content/includes/nginx-one/staged-config-overview.md

@@ -0,0 +1,17 @@
+---
+docs:
+files:
+  - content/nginx-one/how-to/staged-configs/add-staged-config.md
+  - content/nginx-one/how-to/staged-configs/edit-staged-config.md
+---
+It takes time to set up NGINX configuration files can take time. Staged Configurations can help. They work like a draft that uses the features of NGINX One Console.
+You can save your work before you push a configuration to an instance of NGINX.
+
+With Staged Configurations, you can use these features of NGINX One Console:
+
+- Automatic syntax checking
+- Contextual documentation
+- Dynamic analysis of your work in progress
+- Our AI assistant to explain what you've done
+
+Once you've finished your work and have pushed the changes to an Insance or a Config Sync Group, you are then free to delete that Staged Configuration.

content/nginx-one/glossary.md

@@ -20,7 +20,7 @@ This glossary defines terms used in the F5 NGINX One Console and F5 Distributed
 | **Data Plane** | The data plane is the part of a network architecture that carries user traffic. It handles tasks like forwarding data packets between devices and managing network communication. In the context of NGINX, the data plane is responsible for tasks such as load balancing, caching, and serving web content. |
 | **Instance** | An instance is an individual system with NGINX installed. You can group the instances of your choice in a Config Sync Group. When you add an instance to NGINX One, you need to use a data plane key. | 
 | **Namespace** | In F5 Distributed Cloud, a namespace groups a tenant’s configuration objects, similar to administrative domains. Every object in a namespace must have a unique name, and each namespace must be unique to its tenant. This setup ensures isolation, preventing cross-referencing of objects between namespaces. |
-| **Staged Configurations** | Also known as **Staged Configs**. It allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even maanage your **Staged Configurations** through our [API](link to staged configs API page). |
+| **Staged Configurations** | Also known as **Staged Configs**. It allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API](link to staged configs API page). |
 <!-- Set up include, with changelog -->
 | **Tenant** | A tenant in F5 Distributed Cloud is an entity that owns a specific set of configuration and infrastructure. It is fundamental for isolation, meaning a tenant cannot access objects or infrastructure of other tenants. Tenants can be either individual or enterprise, with the latter allowing multiple users with role-based access control (RBAC). |
 {{</bootstrap-table>}}