FINERACT-2383: Modernize and correct README page

Author: steinwinde

README.md

@@ -22,7 +22,7 @@ TABLE OF CONTENTS
   - [How to run for production](#how-to-run-for-production)
   - [How to build the JAR file](#how-to-build-the-jar-file)
   - [How to build the WAR file](#how-to-build-the-war-file)
-  - [How to run using Docker or Podman](#instructions-to-run-using-docker-or-podman)
+  - [How to run using Docker or Podman](#how-to-run-using-docker-or-podman)
   - [How to run on Kubernetes](#how-to-run-on-kubernetes)
     - [General Clusters](#general-clusters)
     - [Using Minikube](#using-minikube)
@@ -34,10 +34,10 @@ TABLE OF CONTENTS
   - [How to download Gradle wrapper](#how-to-download-gradle-wrapper)
   - [How to run Apache RAT (Release Audit Tool)](#how-to-run-apache-rat-release-audit-tool)
   - [How to enable External Message Broker (ActiveMQ or Apache Kafka)](#how-to-enable-external-message-broker-activemq-or-apache-kafka)
-    - [Active MQ](#active-mq)
+    - [ActiveMQ](#activemq)
     - [Kafka](#kafka)
 - [Database and Tables](#database-and-tables)
-  - [If you use MySQL or MariaDB](#if-you-use-mysql-or-mariadb)
+  - [MySQL/MariaDB and UTC timezone](#mysqlmariadb-and-utc-timezone)
 - [Connection Pool Configuration](#connection-pool-configuration)
 - [Checkstyle and Spotless](#checkstyle-and-spotless)
 - [Code Coverage Reports](#code-coverage-reports)
@@ -62,7 +62,6 @@ For the developer wiki, see [Contributor's Zone](https://cwiki.apache.org/conflu
 In any case visit [our JIRA Dashboard](https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824) to find issues to work on, see what others are doing, or open new issues.
 
 
-
 REQUIREMENTS
 ============
 * min. 16GB RAM and 8 core CPU
@@ -71,6 +70,7 @@ REQUIREMENTS
 
 Tomcat (min. v10) is only required, if you wish to deploy the Fineract WAR to a separate external servlet container.  You do not need to install Tomcat to run Fineract. We recommend the use of the self-contained JAR, which transparently embeds a servlet container using Spring Boot.
 
+
 SECURITY
 ============
 If you believe you have found a security vulnerability, [let us know privately](https://fineract.apache.org/#contribute).
@@ -113,7 +113,7 @@ curl --location \
 
 How to run for production
 ---
-Running Fineract to try it out is relatively easy. If you intend to use it in a production environment, be aware that a proper deployment can be complex, costly, and time-consuming. Considerations include: Security, privacy, compliance, performance, service availability, backups, and more. The Fineract project does not provide a comprehensive guide for deploying Fineract in production. You will need to be skilled in enterprise Java applications and more. Or you can pay a vendor for Fineract deployment and maintenance. You will find tips and tricks for deploying and securing Fineract in our official documentation and in the community-maintained wiki.
+Running Fineract to try it out is relatively easy. If you intend to use it in a production environment, be aware that a proper deployment can be complex, costly, and time-consuming. Considerations include: Security, privacy, compliance, performance, service availability, backups, and more. The Fineract project does not provide a comprehensive guide for deploying Fineract in production. You might need skills in enterprise Java applications and more. Alternatively, you could pay a vendor for Fineract deployment and maintenance. You will find tips and tricks for deploying and securing Fineract in our official documentation and in the community-maintained wiki.
 
 
 How to build the JAR file
@@ -151,8 +151,6 @@ The WAR will be created in the `fineract-war/build/libs` directory. Afterwards d
 We recommend using the JAR instead of the WAR file deployment, because it's much easier.
 
 
-<a id="instructions-to-run-using-docker-or-podman"></a>
-
 How to run using Docker or Podman
 ---
 
@@ -454,9 +452,10 @@ and stop and destroy it like this:
 
 Beware that this container database keeps its state inside the container and not on the host filesystem.  It is lost when you destroy (rm) this container.  This is typically fine for development.  See [Caveats: Where to Store Data on the database container documentation](https://hub.docker.com/_/mariadb) regarding how to make it persistent instead of ephemeral.
 
-If you use MySQL or MariaDB
+
+MySQL/MariaDB and UTC timezone
 ---
-With release `1.8.0` we introduced improved date time handling in Fineract. Date time is now stored in UTC, and we enforce UTC timezone even on the JDBC driver, e. g. for MySQL:
+With release `1.8.0` we introduced improved date time handling in Fineract. Date time is stored in UTC, and UTC timezone enforced even on the JDBC driver, e. g. for MySQL:
 
 ```
 serverTimezone=UTC&useLegacyDatetimeCode=false&sessionVariables=time_zone='-00:00'
@@ -476,7 +475,7 @@ Example scenario: If the Fineract instance runs in timezone: GMT+2, and the loca
 
 If a previously used Fineract instance didn't run in UTC (backward compatibility), all prior dates will be read wrongly by MySQL. This can cause issues, when you run the database migration scripts.
 
-Recommendation: You need to shift all dates in your database by the timezone offset that your Fineract instance used.
+Recommendation: Shift all dates in your database by the timezone offset that your Fineract instance used.
 
 
 CONNECTION POOL CONFIGURATION