updated docs

.markdownlint.jsonc

@@ -6,5 +6,6 @@
     // "MD025": false,
     // "MD029": false,
     "MD033": false,
+    "MD034": false,
     "MD036": false
 }

docs/about-me/experience.md

@@ -106,7 +106,7 @@ Stack: MQTT, PostgreSQL, Redis, readingdb, Python, Django, Java, Android, REST
 
 #### Wattman Lite
 
-Working on android as frontend and django as backend. Stack includes MQTT and rest api's for communication to server and rpi devices. 
+Working on android as frontend and django as backend. Stack includes MQTT and rest api's for communication to server and rpi devices.
 
 https://play.google.com/store/apps/details?id=com.zenatix.smartaccontrol&hl=en
 

docs/ai/data-science/datasets.md

@@ -30,9 +30,9 @@ https://github.com/brianfrankcooper/YCSB/wiki/Core-Workloads
 
 ## TPC (Transaction Processing Performance Council)
 
-TPC stands for Transaction Processing Performance Council. It is a non-profit organization that was founded in 1988. The TPC's goal is to define benchmarks for transaction processing and databases. They also distribute objective and verifiable performance data to the industry. 
+TPC stands for Transaction Processing Performance Council. It is a non-profit organization that was founded in 1988. The TPC's goal is to define benchmarks for transaction processing and databases. They also distribute objective and verifiable performance data to the industry.
 
-Here are some TPC benchmarks: 
+Here are some TPC benchmarks:
 
 - TPC-C: Compares the performance of online transaction processing
 - TPC-E: Measures the performance of online transaction processing systems

docs/databases/nosql-databases/readme.md

@@ -11,5 +11,5 @@
 - [YugabyteDB](databases/nosql-databases/yugabytedb.md)
 - [Clickhouse](databases/nosql-databases/clickhouse.md)
 - [Snowflake](databases/nosql-databases/snowflake.md)
-	- [Snowflake Architecture](databases/nosql-databases/snowflake-architecture.md)
+  - [Snowflake Architecture](databases/nosql-databases/snowflake-architecture.md)
 - [Comparisions](databases/nosql-databases/comparisions.md)

docs/devops/devops-intro/sre-site-reliability-engineering.md

@@ -1,10 +1,10 @@
 # SRE (Site Reliability Engineering)
 
-SRE is a method that operates through principles. Instead of prescribing specific solutions, it guides you with best practices. These SRE principles help organizations decide what's best for them. Once you understand the principles, you can apply them in many areas. When considering a new policy or procedure, you can judge it in the context of these principles.  
+SRE is a method that operates through principles. Instead of prescribing specific solutions, it guides you with best practices. These SRE principles help organizations decide what's best for them. Once you understand the principles, you can apply them in many areas. When considering a new policy or procedure, you can judge it in the context of these principles.
 
 All SRE principles align on one ultimate goal: customer satisfaction. By following these SRE core tenets, your efforts will make a positive impact on customers. It’s important to maintain this focus on business value.
 
-### SRE principles vs DevOps principles  
+### SRE principles vs DevOps principles
 
 SRE and DevOps both operate based on a set of principles. Both sets of principles drive alignment towards business goals. Some of their principles overlap. When comparing SRE vs DevOps, the biggest difference is that DevOps principles describe goals. SRE principles describe processes to achieve goals. In this sense, SRE best practices are a way of implementing DevOps principles.