You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 16/umbraco-cms/fundamentals/setup/upgrading/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,9 +46,9 @@ As above, breaking changes that would prevent packages from working other than i
46
46
47
47
For the reasons described, projects always need to be considered case by case when upgrading to new versions.
48
48
49
-
Umbraco communicate's clearly about the breaking changes in release blog posts and on the documented [version specific upgrade details](./version-specific/README.md). There will be extended release candidate periods to ensure upgrades can be tested and to help package developers support new major versions.
49
+
Umbraco communicates about the breaking changes in release blog posts and on the documented [version specific upgrade details](./version-specific/README.md). There will be extended release candidate periods to ensure upgrades can be tested and to help package developers support new major versions.
50
50
51
-
Breaking changes are minimized but there will be cases when such updates are needed. How easy the upgrade will be depends on the breaking changes included in the major and whether your project(s) are impacted by them.
51
+
Breaking changes are minimized but there will be cases when such updates are needed. How straightforward the upgrade will be depends on the breaking changes included in the major and whether your project(s) are impacted by them.
0 commit comments