Answers.Body: <blockquote>
    <p>If your Redactor config included a "formatting" value in the "buttons" array, you need to rename that to "format".</p>
  </blockquote>
  
  <p><a href="https://craftcms.com/help/redactor-ii-configs" rel="nofollow">https://craftcms.com/help/redactor-ii-configs</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T13:13:44.003Z
Answers.Text: Also, the format button tags have changed from"formattingtags" to "formatting",  or it won't work. Like:   
       formatting: ["p", "h2", "h3", "h4"]
Answers.UserDisplayName: noregt
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T22:12:18.197Z
Answers.Text: @noregt Thanks for pointing that out! Just updated the support article.
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-03T17:01:30.020Z
Answers.LastActivityDate: 2015-12-03T17:01:30.020Z
Answers.UserDisplayName: carlcs
Body: <p>I've just updated to 2.5 and am now not able to see or find the text styling option in a text box. We use the formatting option across our site for different headers, quotes, etc. Am I missing something or is the feature gone?</p>
  
Tags: <richtext><format>
Title: Formatting Headers, Quotes, Titles
ThreadText: # Formatting Headers, Quotes, Titles
  
  (Asked by: username_0 on 2015-12-03)
  
  I've just updated to 2.5 and am now not able to see or find the text styling option in a text box. We use the formatting option across our site for different headers, quotes, etc. Am I missing something or is the feature gone?
  
  **Tags:** richtext, format
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-12-03. Score: 3
  
  > If your Redactor config included a "formatting" value in the "buttons" array, you need to rename that to "format".
  
  <https://craftcms.com/help/redactor-ii-configs>
  
  > **Comments:**
  > **username_2**: Also, the format button tags have changed from"formattingtags" to "formatting",  or it won't work. Like:         formatting: ["p", "h2", "h3", "h4"]  
  > **username_3**: @username_2 Thanks for pointing that out! Just updated the support article.  
  
  ---
  
  