Merge branch 'claude/fix-typos-docs-011CUuQH6qFpUzCNozTc417x' into 'master'

Fix typos in blog posts

See merge request postgres-ai/docs!813

Author: NikolayS

blog/20250725-self-driving-postgres.mdx

@@ -115,7 +115,7 @@ These areas naturally became our focus, and we achieved excellent results with o
 
 <p align="center">
   <img
-    src="/assets/blog/20250725-selft-driving-postgres-diagram.svg"
+    src="/assets/blog/20250725-self-driving-postgres-diagram.svg"
     alt="Postgres AI Checkup service: expert-led, AI-assisted comprehensive database health assessment"
     width="625px"
     loading="eager"

blog/20251105-postgres-marathon-2-012.mdx

@@ -32,7 +32,7 @@ pg_basebackup \
 
 Despite having fast NVMe storage and 75 Gbps network capacity, pg_basebackup is fundamentally limited by its single-threaded design. On Postgres versions prior to 18, pg_basebackup typically delivers only 300-500 MiB/s regardless of hardware capabilities.
 
-PostgreSQL 18's [new io_uring support](https://www.postgresql.org/docs/18/runtime-config-resource.html#GUC-IO-METHOD) can speed it up significantly. For our experiment on i4i.32xlarge machines with local NVMe disks, we managed to reach 1.08 GiB/s which is very impressive. But it's still limited. For large databases, this creates a significant operational bottleneck, especially in cases when disk IO and network capactity is high and we could have many gigabytes per second.
+PostgreSQL 18's [new io_uring support](https://www.postgresql.org/docs/18/runtime-config-resource.html#GUC-IO-METHOD) can speed it up significantly. For our experiment on i4i.32xlarge machines with local NVMe disks, we managed to reach 1.08 GiB/s which is very impressive. But it's still limited. For large databases, this creates a significant operational bottleneck, especially in cases when disk IO and network capacity is high and we could have many gigabytes per second.
 
 Multi-threaded pg_basebackup has been a recurring topic on pgsql-hackers over the years ([one](https://www.postgresql.org/message-id/CAEHH7R5sBCRyiu5_qanE741VWGE-LPbVnCdxJZh2U1y1BRPW7A@mail.gmail.com), [two](https://www.postgresql.org/message-id/CADM=Jeg3ZN+kPQpiSfeWCXr=xgpLrq4cBQE5ZviUxygKq3VqiA@mail.gmail.com). However, the feature was never completed or merged. To this day, pg_basebackup remains single-threaded.
 

docs/database-lab/supported-databases.md

@@ -9,7 +9,7 @@ Currently, DBLab Engine fully supports the following [PostgreSQL major versions]
 - 11 (released: 2018-10-18; EOL: 2023-11-09)
 - 12 (released: 2019-10-03; EOL: 2024-11-14)
 - 13 (released: 2020-09-24; EOL: 2025-11-13)
-- 14 (released: 2021-09-31; EOL: 2026-11-12)
+- 14 (released: 2021-09-30; EOL: 2026-11-12)
 - 15 (released: 2022-10-13; EOL: 2027-11-11)
 - 16 (released: 2023-09-14; EOL: 2028-11-09)
 - 17 (released: 2024-09-26; EOL: 2029-11-08)

docs/questions-and-answers.md

@@ -236,7 +236,7 @@ Yes! DBLab supports:
 
 - [Documentation](/docs)
 - [DBLab Engine GitLab repository](https://gitlab.com/postgres-ai/database-lab)
-- [Blog](/blog) – echnical articles and case studies
+- [Blog](/blog) – Technical articles and case studies
 
 ### How do I contact PostgresAI?
 

docs/reference-guides/database-lab-engine-api-reference.md

@@ -19,4 +19,4 @@ DBLab API reference documentation is available at the following locations:
 - [DLE 3.5.x API Reference](https://dblab.readme.io/v3.5.0/)
 - [DBLab 4.0.x API Reference](https://dblab.readme.io/v4.0.0/)
 
-The references are published using the comprehensive ReadMe service. equipped with a developer dashboard and provides code snippets in numerous languages.
+The references are published using the comprehensive ReadMe service, equipped with a developer dashboard and provides code snippets in numerous languages.