message: docs(router): `params` or `queryParams` are not advised against
  According to
  > We no longer speculate about future deprecations. There are no current plans to remove
  > `params` or `queryParams` and there's no benefit to advising against their use.
  PR Close
diff: @@ -155,6 +155,17 @@ It has a great deal of useful information including:
  </td>
  </tr>
  + <tr>
  + <td>
  + <code>params</code>
  + </td>
  + <td>
  +
  + An `Observable` that contains the required and [optional parameters](guide/router-tutorial-toh#optional-route-parameters) specific to the route.
  +
  + </td>
  + </tr>
  +
  <tr>
  <td>
  <code>paramMap</code>
  @@ -179,6 +190,17 @@ It has a great deal of useful information including:
  </td>
  </tr>
  + <tr>
  + <td>
  + <code>queryParams</code>
  + </td>
  + <td>
  +
  + An `Observable` that contains the [query parameters](guide/router-tutorial-toh#query-parameters) available to all routes.
  +
  + </td>
  + </tr>
  +
  <tr>
  <td>
  <code>fragment</code>
  @@ -247,17 +269,6 @@ It has a great deal of useful information including:
  </tr>
  </table>
  -<div class="alert is-helpful">
  -
  -Two older properties are still available; however, their replacements are preferable as they might be deprecated in a future Angular version.
  -
  -* `params`: An `Observable` that contains the required and [optional parameters](guide/router-tutorial-toh#optional-route-parameters) specific to the route. Use `paramMap` instead.
  -
  -* `queryParams`: An `Observable` that contains the [query parameters](guide/router-tutorial-toh#query-parameters) available to all routes.
  -Use `queryParamMap` instead.
  -
  -</div>
  -
  ### Router events
  During each navigation, the `Router` emits navigation events through the `Router.events` property.
  