message: revert more changes
diff: //! ](https://developer.spotify.com/documentation/general/guides/authorization-guide/#client-credentials-flow),
  //! consists on requesting a token to Spotify given some client credentials.
  //! This can be done with [`Spotify::request_client_token`
  -//! ](crate::Spotify::request_client_token), as seen in
  +//! ](crate::client::Spotify::request_client_token), as seen in
  //! [this example
  //! ](https://github.com/ramsayleung/rspotify/blob/master/examples/album.rs).
  //!
  //! instead. In a nutshell, these are the steps you need to make for this:
  //!
  //! 0. Generate a request URL with [`Spotify::get_authorize_url`
  -//! ](crate::Spotify::get_authorize_url).
  +//! ](crate::client::Spotify::get_authorize_url).
  //! 1. The user logs in with the request URL, which redirects to the redirect
  //! URI and provides a code in the parameters. This happens on your side.
  //! 2. The code obtained in the previous step is parsed with
  //! [`Spotify::parse_response_code`
  -//! ](crate::Spotify::parse_response_code).
  +//! ](crate::client::Spotify::parse_response_code).
  //! 3. The code is sent to Spotify in order to obtain an access token with
  //! [`Spotify::request_user_token`
  -//! ](crate::Spotify::request_user_token) or
  +//! ](crate::client::Spotify::request_user_token) or
  //! [`Spotify::request_user_token_without_cache`
  -//! ](crate::Spotify::prompt_for_user_token_without_cache).
  +//! ](crate::client::Spotify::prompt_for_user_token_without_cache).
  //! 4. Finally, this access token can be used internally for the requests.
  //! This access token may expire relatively soon, so it can be refreshed
  //! with the refresh token (obtained in the third step as well) using
  //! [`Spotify::refresh_user_token`
  -//! ](crate::Spotify::refresh_user_token) or
  +//! ](crate::client::Spotify::refresh_user_token) or
  //! [`Spotify::refresh_user_token_without_cache`
  -//! ](crate::Spotify::refresh_user_token_without_cache).
  +//! ](crate::client::Spotify::refresh_user_token_without_cache).
  //! Otherwise, a new access token may be generated from scratch by repeating
  //! these steps, but the advantage of refreshing it is that this doesn't
  //! require the user to log in, and that it's a simpler procedure.
  //!
  //! If you're developing a CLI application, you might be interested in the
  //! `cli` feature, which brings the [`Spotify::prompt_for_user_token`
  -//! ](crate::Spotify::prompt_for_user_token) and
  +//! ](crate::client::Spotify::prompt_for_user_token) and
  //! [`Spotify::prompt_for_user_token_without_cache`
  -//! ](crate::Spotify::prompt_for_user_token_without_cache)
  +//! ](crate::client::Spotify::prompt_for_user_token_without_cache)
  //! methods. These will run all the authentication steps. The user wil log in
  //! by opening the request URL in its default browser, and the requests will be
  //! performed automatically.
  