Skip to content

Commit 25ee2fb

Browse files
authored
Typo fix
1 parent 0fb6f0f commit 25ee2fb

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/operator-service-manager/best-practices-onboard-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ We recommend that you first onboard and deploy your simplest NFs (one or two cha
2222
- The Azure Operator Service Manager command-line interface (CLI) extension assists with the publishing of network function definitions (NFDs) and NSDs. Use this tool as the starting point for creating new NFDs and NSDs. Consider using the CLI to create the initial files. Then edit them to incorporate infrastructure components before you publish.
2323

2424
## Publisher considerations
25-
- We recommend that you create a single publisher per NF supplier, or per NF type per NF supplier, where the NF supplier may provide more then one NF type. This practice;
25+
- We recommend that you create a single publisher per NF supplier, or per NF type per NF supplier, where the NF supplier may provide more than one NF type. This practice;
2626
- Provides for the most optimal support, maintenance, and governance experience, by preventing proliferation of publishers. Especially during upgrade activities where the same action is often executed across many NFs.
2727
- Lowers total operating costs by reducing the number of publisher backing resources, like ACR or Storage Accounts.
2828
- Simplifies the network service design (NSD), where it may consist of multiple NFs from multiple vendors.

0 commit comments

Comments
 (0)