Skip to content

docs: Fix 2 typos (vender -> vendor) #1353

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.

Sign up for GitHub

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
jonathannorris merged 1 commit into from
Mar 27, 2026
Merged

docs: Fix 2 typos (vender -> vendor) #1353

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/reference/concepts/02-provider.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ The following naming recommendations can be used to ensure consistency between p
If you're creating a new repository, it's recommended that you use one the following naming conventions:

- `openfeature-provider-<language name>`
- `<vender/tool name>-openfeature-provider-<language name>`
- `<vendor/tool name>-openfeature-provider-<language name>`

:::note

Expand All @@ -75,7 +75,7 @@ Ultimately, it's up to the publisher to decide what name makes the most sense.
However, the following items should be used in the package name:

- OpenFeature (can also be stylized as openfeature or open-feature)
- Vender/tool name
- Vendor/tool name
- The word `provider` should be included in the name

An example of what it could look like in NPM: `@openfeature/flagd-provider`
Expand Down
Loading