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

Commit a278690

Browse files
doboothkeharper
andauthored
Update src/guides/v2.3/comp-mgr/upgrade-best-practices.md
Co-authored-by: Kevin Harper <keharper@users.noreply.github.com>
1 parent 913ddb8 commit a278690

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/guides/v2.3/comp-mgr/upgrade-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ It is important to understand the variables that determine the complexity of an
1616

1717
The level of effort to upgrade your {{site.data.var.ee}} instance depends upon these factors:
1818

19-
* **How you have built your site?** The amount of custom work and the number of installed 3rd-party modules strongly affects the complexity of an upgrade. The quality of the custom work and modules can determine whether an upgrade will go smoothly.
19+
* **How did you build your site?** The amount of custom work and the number of installed 3rd-party modules strongly affects the complexity of an upgrade. The quality of the custom work and modules can determine whether an upgrade will go smoothly.
2020

2121
* **Are you skipping multiple releases?** Skipping releases will makes the next upgrade more complex, upgrading from consequent versions will make the process easier and cheaper.
2222

0 commit comments

Comments
 (0)