Skip to content

fix: Address typo update metadata for Add a Staged Configuration topic #549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 14, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@ weight: 100
# Creates a table of contents and sidebar, useful for large documents
toc: true
# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
type: tutorial
nd-content-type: how-to
# Intended for internal catalogue and search, case sensitive:
# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
product:
nd-product: NGINX One
---

## Overview
Expand All @@ -33,7 +33,7 @@ You can add a Staged Configuration from:
- An existing Config Sync Group
- An existing Staged Configuration

To start the process from NGINX One Console, select **Manage > Staged Configruations**. Select **Add Staged Configuration**.
To start the process from NGINX One Console, select **Manage > Staged Configurations**. Select **Add Staged Configuration**.

The following sections start from the **Add Staged Configuration** window that appears.

Expand Down
Loading