message: Polish the "Using Abseil in WebRTC" docs
  Move the "How to depend on Abseil" section higher up to make it more
  visible, and fix a few language nits.
  Cr-Commit-Position: refs/heads/master@{#32422}
diff: @@ -9,6 +9,17 @@ adds the first use.
  [abseil]: https://abseil.io/about/
  +
  +## How to depend on Abseil
  +
  +For build targets of type `rtc_library`, `rtc_source_set` and
  +`rtc_static_library`, dependencies on Abseil need to be listed in `absl_deps`
  +instead of `deps`.
  +
  +This is needed in order to support the Abseil component build in Chromium. In
  +that build mode, WebRTC will depend on a monolithic Abseil build target that
  +will generate a shared library.
  +
  ## **Allowed**
  * `absl::InlinedVector`
  @@ -63,12 +74,3 @@ has decided if they will change `absl::Span` to match.
  These are optimized for speed, not binary size. Even `StrCat` calls
  with a modest number of arguments can easily add several hundred bytes
  to the binary.
  -
  -## How to depend on Abseil
  -
  -For build targets `rtc_library`, `rtc_source_set` and `rtc_static_library`,
  -dependencies on Abseil need to be listed in `absl_deps` instead of `deps`.
  -
  -This is needed in order to support the Abseil component build in Chromium. In
  -such build mode, WebRTC will depend on a unique Abseil build target what will
  -generate a shared library.
  