Skip to content
This repository was archived by the owner on Nov 29, 2024. It is now read-only.

Update planning-changes.md - fix minor typo #583

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update planning-changes.md - fix minor typo #583

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/_manage/integration-changes/planning-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Before making updates to your integration, it's important to consider the potent

## Effects of Different Changes (Versioning Matrix)

The matrix below illustrates the impact of different changes on ypur users. For public integrations, this will affect promotion and whether migration is possible. Refer to our best practices to facilitate the upgrade process for yourself and your users.
The matrix below illustrates the impact of different changes on your users. For public integrations, this will affect promotion and whether migration is possible. Refer to our best practices to facilitate the upgrade process for yourself and your users.

Columns:
* Add: Adding a net new component
Expand Down Expand Up @@ -67,4 +67,4 @@ Change scenarios marked as _Depends_ with no linked best practice can vary widel



If your change is not listed, make sure to still consider whether it changes keys, requires users to provide _new_ info, or revokes functionality.
If your change is not listed, make sure to still consider whether it changes keys, requires users to provide _new_ info, or revokes functionality.