Update exception filter heading and TOC

README.md

@@ -26,6 +26,7 @@ This is the Ruby library for Rollbar. It will instrument many kinds of Ruby appl
 - [Data sanitization (scrubbing)](#data-sanitization-scrubbing)
 - [Including additional runtime data](#including-additional-runtime-data)
 - [Exception level filters](#exception-level-filters)
+  - [Dyanmic levels](#dynamic-levels)
 - [Before process hook](#before-process-hook)
 - [Transform hook](#transform-hook)
 - [The Scope](#the-scope)
@@ -501,7 +502,7 @@ This behavior applies to uncaught exceptions, not direct calls to `Rollbar.error
 Rollbar.error(exception, :use_exception_level_filters => true)
 ```
 
-### Advanced Usage
+### Dynamic levels
 
 You can also specify a callable object (any object that responds to `call`) which will be called with the exception instance. For example, you can have a single error reported at different levels using the following code:
 
@@ -511,7 +512,7 @@ config.exception_level_filters.merge!({
 })
 ```
 
-## [Before process hook](#before-process-hook)
+## Before process hook
 
 Before we process data sent to Rollbar.log (or Rollbar.error/info/etc.) to build and send the payload, the gem will call the handlers defined in `configuration.before_process`. This handlers should be `Proc` objects or objects responding to `#call` method. The received argument is a `Hash` object with these keys:
 
@@ -533,7 +534,7 @@ Rollbar.configure do |config|
 end
 ```
 
-## [Transform hook](#transform-hook)
+## Transform hook
 
 After the payload is built but before it it sent to our API, the gem will call the handlers defined in `configuration.transform`. This handlers should be `Proc` objects or objects responding to `#call` method. The received argument is a `Hash` object with these keys:
 
@@ -558,7 +559,7 @@ Rollbar.configure do |config|
 end
 ```
 
-## [The Scope](#the-scope)
+## The Scope
 
 The scope an object, an instance of `Rollbar::LazyStore` that stores the current context data for a certain moment or situation. For example, the Rails middleware defines the scope in a way similar to this: