PB-480: Update content type styling concepts

bdenham · bdenham · commit 25cdc55d3045 · 2020-04-13T05:07:17.000-05:00
Removed angle brackets in heading to fix topic's right-side TOC
diff --git a/docs/how-to/how-to-use-attributes-for-styling.md b/docs/how-to/how-to-use-attributes-for-styling.md
@@ -294,7 +294,7 @@ To aid in our discussion of these configuration nodes and how to use them, we wi
 {: .bs-callout .bs-callout-info }
 The `<tag>` and `<html>` nodes are beyond the scope of this topic, but like the other nodes, they also map to fields in a form. In this case, the `<tag>` node maps to the Heading's `heading_type` field and the `<html>` node maps to the `heading_text` field from the `pagebuilder_heading_form.xml`.
 
-### Understanding and using `<style>` nodes
+### Understanding and using `style` nodes
 
 By configuring `<elements>` with `<style>` nodes, you can provide end users with a form field that changes a _specific_ CSS property, such as we did with `opacity`.
 
@@ -333,13 +333,13 @@ Each `<style>` node defined for the element's configuration gets added to the DO
 </h2>
 ```
 
-### Using `<attribute>` nodes instead of `<style>` nodes
+### Deciding to use `attribute` or `style` configurations
 
 As mentioned, adding an `<attribute>` node to an `element` configuration gives you a way to provide end users with a form field that can use _CSS classes_, allowing you to change _several_ CSS properties at once. This can be more powerful that using `<style>` configurations that can only change single CSS properties. But depending on your use case, you may not need to use `<attribute>` configurations.
 
-Using `<attribute>` or `<style>` configurations is transparent to end users. They're simply interacting with field options to change content styling. But for you, the developer, the choice really depends on how much you need to change the element. If the user option needs to change the element significantly, you may want to use an `<attribute>` so you can apply CSS classes to the element. And if the user option is focused on making a simple property change to the element, you can use a `<style>` configuration.
+Using `<attribute>` or `<style>` configurations is transparent to end users. But for you, the developer, the choice really depends on how much you need to change the element. If the user option needs to change the element significantly, you may want to use an `<attribute>` so you can apply CSS classes to the element. And if the user option is focused on making a simple property change to the element, you can use a `<style>` configuration.
 
-### Understanding the `<css>` node {#understandthecssnode}
+### Understanding the `css` node {#understandthecssnode}
 
 The `<css>` config node is a bit different from the `<attribute>` and `<style>` nodes. The `<css>` node wasn't designed to be added to an element more than once like the other two nodes. Instead, it was designed to capture multiple CSS classes from a single form field and render those classes to the DOM within the `class` attribute. For this reason, it is currently not possible to add CSS classes to an element's `class` attribute from other form fields.
 
