docs: [#1261] fix doc errors in tracker-core

Author: josecelano

packages/tracker-core/src/authentication/key/mod.rs

@@ -6,7 +6,7 @@
 //!
 //! There are services to [`generate_key`]  and [`verify_key_expiration`]  authentication keys.
 //!
-//! Authentication keys are used only by [`HTTP`](crate::servers::http) trackers. All keys have an expiration time, that means
+//! Authentication keys are used only by HTTP trackers. All keys have an expiration time, that means
 //! they are only valid during a period of time. After that time the expiring key will no longer be valid.
 //!
 //! Keys are stored in this struct:
@@ -112,7 +112,7 @@ pub fn generate_key(lifetime: Option<Duration>) -> PeerKey {
 ///
 /// # Errors
 ///
-/// Will return a verification error [`crate::authentication::key::Error`] if
+/// Will return a verification error [`enum@crate::authentication::key::Error`] if
 /// it cannot verify the key.
 pub fn verify_key_expiration(auth_key: &PeerKey) -> Result<(), Error> {
     let current_time: DurationSinceUnixEpoch = CurrentClock::now();

packages/tracker-core/src/databases/driver/mod.rs

@@ -1,7 +1,4 @@
 //! Database driver factory.
-//!
-//! See [`databases::driver::build`](crate::core::databases::driver::build)
-//! function for more information.
 use mysql::Mysql;
 use serde::{Deserialize, Serialize};
 use sqlite::Sqlite;

packages/tracker-core/src/databases/error.rs

@@ -1,6 +1,6 @@
 //! Database errors.
 //!
-//! This module contains the [Database errors](crate::core::databases::error::Error).
+//! This module contains the [Database errors](crate::databases::error::Error).
 use std::panic::Location;
 use std::sync::Arc;
 

packages/tracker-core/src/databases/mod.rs

@@ -4,8 +4,8 @@
 //!
 //! There are two implementations of the trait (two drivers):
 //!
-//! - [`Mysql`](crate::core::databases::mysql::Mysql)
-//! - [`Sqlite`](crate::core::databases::sqlite::Sqlite)
+//! - `Mysql`
+//! - `Sqlite`
 //!
 //! > **NOTICE**: There are no database migrations. If there are any changes,
 //! > we will implemented them or provide a script to migrate to the new schema.

packages/tracker-core/src/lib.rs

@@ -25,7 +25,6 @@
 //!   - [Torrents](#torrents)
 //!   - [Peers](#peers)
 //! - [Configuration](#configuration)
-//! - [Services](#services)
 //! - [Authentication](#authentication)
 //! - [Statistics](#statistics)
 //! - [Persistence](#persistence)
@@ -342,18 +341,6 @@
 //!
 //! Refer to the [`configuration` module documentation](https://docs.rs/torrust-tracker-configuration) to get more information about all options.
 //!
-//! # Services
-//!
-//! Services are domain services on top of the core tracker domain. Right now there are two types of service:
-//!
-//! - For statistics: [`crate::packages::statistics::services`]
-//! - For torrents: [`crate::core::torrent::services`]
-//!
-//! Services usually format the data inside the tracker to make it easier to consume by other parts.
-//! They also decouple the internal data structure, used by the tracker, from the way we deliver that data to the consumers.
-//! The internal data structure is designed for performance or low memory consumption. And it should be changed
-//! without affecting the external consumers.
-//!
 //! Services can include extra features like pagination, for example.
 //!
 //! # Authentication