Skip to content

Commit 5b80811

Browse files
authored
Update configuration-guide.md
1 parent 5dfcc33 commit 5b80811

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/operator-service-manager/configuration-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This article provides Azure Operator Service Manager (AOSM) guidelines to optimi
1515
JSON Schema is an Internet Engineering Task Force (IETF) standard providing a format for what JSON data is required for a given application and how to interact with it. Applying such standards for a JSON document lets you enforce consistency and data validity across JSON data
1616

1717
### Where is JSON schema used
18-
* AOSM service uses JSON schema notation as a meta-schema within CGS `ConfigurationGroupSchemaPropertiesFormat` object `schemaDefinition` properties. For more information on CGS, see the [swagger documentation](https://learn.microsoft.com/en-us/rest/api/hybridnetwork/configuration-group-schemas/create-or-update?view=rest-hybridnetwork-2023-09-01&tabs=HTTP#configurationgroupschemapropertiesformat).
18+
* AOSM service uses JSON schema notation as a meta-schema within CGS `ConfigurationGroupSchemaPropertiesFormat` object `schemaDefinition` properties. For more information on CGS, see the [swagger documentation](https://learn.microsoft.com/en-us/rest/api/hybridnetwork/configuration-group-schemas/create-or-update).
1919
* AOSM service allows the designer and publisher to specify the JSON schema where operator must provide data (JSON Values) when instantiating an SNS/NF.
2020
* AOSM service allows the meta-schema properties be optional or required. Where a property is marked required, it must be specified in the values Json.
2121

@@ -27,7 +27,7 @@ For the CGS meta-schema, AOSM implements supports for JSON standard keywords on
2727
* For numeric types, keyword support isn't limited or filtered. See JSON Schema - [numeric](https://json-schema.org/understanding-json-schema/reference/numeric)
2828

2929
## Optional and Required fields
30-
A property is declared optional by including a `required` keyword which omitts the optional property. If the `required` keyword is not specified, then all properties are considered required. At leaat one required property type is needed to support an optional property type.
30+
A property is declared optional by including a `required` keyword, which omits the optional property. If the `required` keyword isn't specified, then all properties are considered required. At least one required property type is needed to support an optional property type.
3131

3232
```json
3333
{

0 commit comments

Comments
 (0)