Update troubleshooting and remove repo files

Author: Andriciuc

docs/remove-repo-ver.md

@@ -1,31 +1,28 @@
-# Removed repository versions
+# Repository 404 errors and removed versions
 
-## Overview
+Some Percona Distribution for PostgreSQL repository versions are no longer available and may return a `404 Not Found` error when accessed. This happens because these versions have been removed from the repository.
 
-Some Percona Distribution for PostgreSQL repository versions are no longer available and may return a `404 Not Found` error when accessed. The affected versions are:
+The affected versions are:
 
-- ppg-14.19
-- ppg-15.14
-- ppg-16.10
-- ppg-17.6
+- `ppg-14.19`
+- `ppg-15.14`
+- `ppg-16.10`
+- `ppg-17.6`
 
 ## Reason for removal
 
-These versions were part of a release that included known issues affecting stability and reliability (also referred to internally as the "assertion release").
+These versions were part of a release that included known issues affecting stability and reliability.
 
 To prevent unintended usage, these repositories were removed from distribution.
 
+These versions are not recommended for production use.
+
 ## What should you do instead?
 
 Use the latest available minor version for your PostgreSQL major version.
 
-Example:
-
-- Instead of `ppg-16.10`, use the latest `ppg-16.x`
-
-See [installation guide]
+Examples:
 
-## Additional context
+- Instead of `ppg-17.6`, use the latest `ppg-17.x`
 
-For more details, see the relevant release notes:
-- [link to release notes]
+For installation and upgrade instructions, see the [minor upgrade guide](minor-upgrade.md).

docs/troubleshooting.md

@@ -1,16 +1,18 @@
-# Troubleshooting guide
+# Troubleshooting guide overview
 
 This guide helps you identify and resolve common issues when installing, configuring, or running Percona Server for PostgreSQL 17.
 
 If you're looking for general information or usage tips, check the [FAQ](faq.md).
 
-## Cannot create a table. Permission denied in schema `public`
+## Common issues
+
+### Cannot create a table. Permission denied in schema `public`
 
 Every database in PostgreSQL has a default schema called `public`. A schema stores database objects like tables, views, indexes and allows organizing them into logical groups.
 
 When you create a table without specifying a schema name, it ends up in the `public` schema by default.
 
-Starting with PostgreSQL 15, non-database owners cannot access the `public` schema. Therefore, you can either grant privileges to the database for your user using the [GRANT](https://www.postgresql.org/docs/{{pgvesrion}}/sql-grant.html) command or create your own schema to insert the data.
+Starting with PostgreSQL 15, non-database owners cannot access the `public` schema. Therefore, you can either grant privileges to the database for your user using the [GRANT](https://www.postgresql.org/docs/{{pgversion}}/sql-grant.html) command or create your own schema to insert the data.
 
 To create a schema, use the following statement: