fix: 🐛 fix sidebar items padding

Author: bcamarneiro

docs/learn/delivery-acknowledgements.md

@@ -8,8 +8,6 @@ tags:
 sidebarCollapsible: false
 ---
 
-import Author from '@site/src/components/Author';
-
 ## Overview
 
 When a client signs a message, it creates a Delivery Acknowledgement that confirms a successful service computation delivery by a node. This [process](#node-vs-client-process-flow) ensures the immutability and integrity of the message (the client cannot change or reverse it) and also includes metadata about the commodities consumed by the node during the service execution. This metadata helps in calculating the reward that the node will receive.
@@ -75,10 +73,3 @@ Learn more about it in the [Content Addressing](/docs/learn/the-network#content-
 ## Delivery Acknowledgement Customization
 
 A Service can have a custom configuration to specify how Delivery Acknowledgements should behave or work. Patterns and conventions should be expected to emerge from the Service builder community and best practices.
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/learn/index.md

@@ -10,8 +10,6 @@ tags:
   - whitepaper
 ---
 
-import Author from '@site/src/components/Author';
-
 ## Introduction
 
 The Core of Fleek Network offers a foundational layer to enable developers to build and deploy Edge Services efficiently. It abstracts away the development complexities of consensus, cryptography, storage and peer-to-peer networking, etc, to simplify things conceptually. It frees developers and teams to focus on what matters the most to reach business goals.
@@ -47,10 +45,3 @@ When a client requests a service, the protocol determines the best route to the
 Once the computation is successful, the data streaming routes to the client. On-client request fulfillment, a proof of delivery is generated containing cryptographically secured metadata about the original request, any parts involved and the resources consumed.
 
 The Delivery Acknowledgements are stored locally in the participating node memory pools, rolled up to the protocol consensus consistently throughout the epoch (about 24h). This agreement is formed by a random committee of any healthy Nodes that use the information provided to reward the Nodes fairly.
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/learn/services.md

@@ -18,8 +18,6 @@ tags:
 - toolkit
 ---
 
-import Author from '@site/src/components/Author';
-
 ## Overview 
 
 A Fleek Network Service is a modular application that runs on nodes and allows users to perform well-defined functions or some specific tasks. Services are scalable and performant due to edge computation and networking features provided by the core principles of the network.
@@ -137,10 +135,3 @@ This causes long finalization times and a reduction in block speeds on Layer-1,
 In Fleek Network, a service builder can offer an alternative to a Layer-2 sequencer, that is decentralized and more reliable by batching and posting to Layer-1 settlement contracts. With equivalent Layer-2 settlement times.
 
 An additional benefit can be enabling end-user gasless transaction submissions by disregarding a Layer-2 gas token to submit transactions to Layer-1.
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/learn/the-network.md

@@ -17,7 +17,6 @@ tags:
 sidebarCollapsible: false
 ---
 
-import Author from '@site/src/components/Author';
 import Ports from '../../guides/partials/_ports.mdx';
 
 ## Protocol
@@ -401,10 +400,3 @@ The Fleek Network binary process is the program that's been compiled down to mac
 A JSON-RPC (JavaScript Object Notation Remote Procedure Call) is a protocol that enables communication between client and server applications. The [Fleek Network JSON-RPC](https://fleek-network.github.io/lightning/api-documentation/?202308171515) API enables JSON-RPC interaction with Fleek Network Node.
 
 Fleek Network JSON-RPC API reference documentation is available at [https://fleek-network.github.io/lightning/api-documentation](https://fleek-network.github.io/lightning/api-documentation).
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/node/analyzing-logs.md

@@ -7,7 +7,6 @@ tags:
   - diagnostic
 ---
 
-import Author from '@site/src/components/Author';
 
 ## Analyzing Logs
 
@@ -86,10 +85,3 @@ In any case, you can use the Docker command to analyze the logs. If you have sti
 sudo docker logs -f lightning-node
 ```
 :::
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/node/health-check.md

@@ -8,8 +8,6 @@ tags:
   - node status
 ---
 
-import Author from '@site/src/components/Author';
-
 ## TL;DR: Run the command
 
 A script is available to do and provide a health check overview:
@@ -104,10 +102,3 @@ If the request is successful, you should get the result `pong` as follows:
 ```
 
 Any other response, such as errors determine that the node is not healthy.
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/node/index.md

@@ -7,8 +7,6 @@ tags:
   - build
 ---
 
-import Author from '@site/src/components/Author';
-
 ## Overview
 
 This section provides instructions to help you build a **Fleek Network Node**, it's aimed at everybody willing to learn and cultivate knowledge as a node operator.
@@ -40,11 +38,3 @@ While we do our best to provide the clearest instructions, there's always space
 :::
 
 **Ready?** Start by checking the [server requirements](/docs/node/requirements)
-
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/node/install.md

@@ -18,7 +18,6 @@ tags:
 - manual
 ---
 
-import Author from '@site/src/components/Author';
 import GitCloneOptions from '../../guides/partials/_git-clone-options.mdx';
 import CreateAUser from '../../guides/partials/_create-a-user.mdx';
 import SetUserPathInConfigToml from '../../guides/partials/_set-user-path-config-toml.mdx';
@@ -708,10 +707,3 @@ Learn how to manage the Systemd Service by reading the section [systemd service]
 ## Frequently Used Commands (Quick Reference)
 
 A quick reference of the most Frequently Used Commands are available for [Native](/references/Lightning%20CLI/frequently-used-commands-for-native-setup) and [Docker](/references/Docker/frequently-used-commands-for-docker-setup) setups. If you'd like a more in depth explanation of the commands, check the [health check](/docs/node/health-check), [analyzing logs](/docs/node/analyzing-logs), [systemd service](/docs/node/systemd-service) and [guides](/guides) sections separately.
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/node/lightning-cli.md

@@ -9,7 +9,6 @@ tags:
   - lgtn
 ---
 
-import Author from '@site/src/components/Author';
 import InfoNetworkParticipation from '../../guides/partials/_info_network_participation.mdx';
 import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx';
 import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx';
@@ -167,10 +166,3 @@ Options:
   -v...                      Increases the level of verbosity (the max level is -vvv)
   -h, --help                 Print help
 ```
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>

docs/node/requirements.md

@@ -8,7 +8,6 @@ tags:
 sidebarCollapsible: false
 ---
 
-import Author from '@site/src/components/Author';
 import Ports from '../../guides/partials/_ports.mdx';
 
 ## Requirements
@@ -57,10 +56,3 @@ The recommended number of CPU cores is a minimum of 4 with a minimum CPU speed o
 ### Memory
 
 A minimum of 32 GB of memory (RAM) is required and a reasonable amount of disk space for the installation and running processes, which at the minimum should be around 20 GB.
-
-<Author
-    name="Helder Oliveira"
-    image="https://github.com/heldrida.png"
-    title="Software Developer + DX"
-    url="https://github.com/heldrida"
-/>