[Docs] [README] Update Docs (Force Push)

- [+] chore(README.md): update feature descriptions
- [+] fix(README.md): fix typo in feature description

README.md

@@ -16,21 +16,21 @@ This project aims to provide a straightforward and scalable approach to creating
 
 ## Features
 
-- **🔗 Shorten URLs**: The service allows users to convert long URLs into short, manageable identifiers that redirect to the original URLs. This makes the links easier to share on platforms with character limits or for readability purposes.
+- **🔗 Shorten URLs**: Transform lengthy URLs into concise, easy-to-share identifiers. These short links redirect users to the original URLs, making them more suitable for sharing on social media, in printed materials, or anywhere space is at a premium.
 
-- **↪️ Redirection**: When a client accesses a short link, the service performs an HTTP or HTTPS redirect to the original, long URL associated with the short identifier.
+- **↪️ Efficient Redirection**: Utilizes HTTP/HTTPS redirection to seamlessly guide users from a short link to the original URL. The redirection process is designed to be quick and reliable, ensuring a smooth user experience.
 
-- **🔌 Simple Integration**: The service exposes RESTful API endpoints for creating, retrieving, updating, and deleting shortened URLs, which can be easily used by external applications or services.
+- **🔌 RESTful API Integration**: Offers a suite of RESTful endpoints (`POST`, `GET`, `PUT`, `DELETE`) for managing shortened URLs. This allows for straightforward integration with other applications or services, facilitating automation and interoperability.
 
-- **🏴‍☠️ Dependency Injection (Greetz Thx to: Gopher Unit Hacker)**: The application's architecture includes dependency injection for core components like the logger and the Datastore client. This design pattern enhances testability and maintainability by decoupling the components and their dependencies.
+- **🏴‍☠️ Advanced Dependency Injection**: Employs dependency injection for essential components, such as the logger and the Datastore client, to promote a modular and testable codebase. This approach allows for swapping components without altering the codebase significantly.
 
-- **⚖️ Scalability**: Designed to be deployed as a containerized service, the application is built to handle high loads and can be scaled horizontally in a cloud environment.
+- **⚖️ Designed for Scalability**: The service's containerized architecture is optimized for scalability. It's prepared to handle increasing loads and can be scaled out across multiple instances in a cloud-based environment to accommodate growing demand.
 
-- **🛡️ Security**: Access to certain API endpoints can be restricted to internal services using middleware that checks for a specific secret value, thereby enhancing the security of the application.
+- **🛡️ Enhanced Security Measures**: Implements security measures to protect sensitive API endpoints. Middleware validates secret tokens to ensure that only authorized services can access certain operations, thus safeguarding against unauthorized use.
 
-- **🔎 Logging and Monitoring**: Structured logging is implemented using the `zap` library, which facilitates real-time monitoring and debugging of the application.
+- **🔎 Structured Logging**: Incorporates the `zap` logging library for structured, efficient logging. This supports real-time monitoring and aids in the rapid diagnosis and resolution of issues, contributing to the overall reliability of the service.
 
-- **🪫 Graceful Shutdown**: The service can handle shutdown signals and terminate gracefully, ensuring that ongoing operations are completed and resources are released properly.
+- **🪫 Graceful Shutdown Capability**: The service is designed to respond to shutdown signals appropriately, finishing active operations and releasing resources in an orderly manner. This feature is crucial for maintaining data integrity and service availability during deployments and maintenance.
 
 ## Environment Configuration