PB-518: Docs housework for 1.3 release

bdenham · bdenham · commit 019951c06a74 · 2020-04-27T20:55:45.000-05:00
Changed upgrade topic name
diff --git a/docs/how-to/how-to-use-upgrade-library.md b/docs/how-to/how-to-use-upgrade-library.md
@@ -1,4 +1,4 @@
-# How to use the content type upgrade library
+# How to upgrade content types
 
 Before version 1.3, changes to a content-type configuration could (and usually would) break the existing content that was saved with the previous configuration. Why? Because a content type's configuration maps data from its source (the master format) to its display templates. So when the configuration mapping changes, the display of existing content might also change. With significant configuration changes, data (such as styles, attributes, and html) is lost. Such changes cause existing content to appear incorrectly, or not at all.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# How to use the content type upgrade library`
	`1`	`+# How to upgrade content types`
`2`	`2`
`3`	`3`	Before version 1.3, changes to a content-type configuration could (and usually would) break the existing content that was saved with the previous configuration. Why? Because a content type's configuration maps data from its source (the master format) to its display templates. So when the configuration mapping changes, the display of existing content might also change. With significant configuration changes, data (such as styles, attributes, and html) is lost. Such changes cause existing content to appear incorrectly, or not at all.
`4`	`4`