Skip to content

Commit 1db0bb3

Browse files
committed
docs: format
1 parent e8ef0ba commit 1db0bb3

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

content/nginx-one/api/nginx_configuration.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Use the following curl command to retrieve the current NGINX Config for a specif
3434
- `<token-value>`: Your API Token.
3535

3636
{{< call-out "note" >}}
37-
To update the NGINX Config for a Config Sync Group, replace `instances` with `config-sync-groups` or `staged-configs` and use the object_id of the Config Sync Group or Staged Config in the URL.
37+
To update the NGINX Config for a Config Sync Group or Staged Config, replace `instances` with `config-sync-groups` or `staged-configs` and use the object_id of the Config Sync Group or Staged Config in the URL.
3838
{{< /call-out>}}
3939

4040
The response will include the current NGINX Config in JSON format. This response is saved to a file (e.g., `current_config.json`) for editing.
@@ -77,6 +77,7 @@ You can modify the NGINX Config using either `PUT` or `PATCH` requests. The `PUT
7777
- Leave out file `contents` to remove the file from the NGINX Config.
7878
- Include file `contents` to add or update the file in the NGINX Config. File `contents` must be base64 encoded. File `contents` can be an empty string to create an empty file.
7979
- `config_version` should be included to ensure you're updating the correct version of the configuration. You can get the current `config_version` from the response of the `GET` request.
80+
8081
For example, to update only the `/etc/nginx/nginx.conf` file in the NGINX Config, your `partial_update_config.json` might look like this:
8182
```json
8283
{

0 commit comments

Comments
 (0)