Skip to content

Commit 876d27b

Browse files
committed
Update CSG page
1 parent df4776d commit 876d27b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/nginx-one/how-to/config-sync-groups/manage-config-sync-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Config Sync Groups support configuration inheritance and persistance. If you've
3737

3838
On the other hand, if you remove all instances from a Config Sync Group, the original configuration persists. In other words, the group retains the configuration from that first instance (or the original configuration). Any new instance that you add later still inherits that configuration.
3939

40-
{{< tip >}}You can use _unmanaged_ certificates. Your actions can affect the [Config Sync Group status](#config-sync-group-status). For future instances on the data plane, if it:
40+
{{< tip >}}You can use _unmanaged_ certificates. NGINX One Console collects _only_ the metadata shown in the console. It does not include the content of the certificate. Your actions can affect the [Config Sync Group status](#config-sync-group-status). For future instances on the data plane, if it:
4141

4242
- Has unmanaged certificates in the same file paths as defined by the NGINX configuration as the Config Sync Group, that instance will be [**In Sync**](#config-sync-group-status).
4343
- Will be [**Out of Sync**](#config-sync-group-status) if the instance:

0 commit comments

Comments
 (0)