Updated builds comparison after the review

documentation/docs/features.md

@@ -1,26 +1,26 @@
 # Build comparison
 
-We provide `pg_tde` builds for both PostgreSQL Community and [Percona Server for PostgreSQL](https://docs.percona.com/postgresql/17/). The difference between the builds is in the set of included features which in its turn depends on the Storage Manager API. While PostgreSQL Community uses the default Storage Manager API, Percona Server for PostgreSQL extends the Storage Manager API enabling to integrate custom storage managers.
+We provide `pg_tde` builds for both PostgreSQL Community and [Percona Server for PostgreSQL](https://docs.percona.com/postgresql/latest/postgresql-server.html). The difference between the builds is in the set of included features which in turn depends on the Storage Manager API. While PostgreSQL Community uses the default Storage Manager API, Percona Server for PostgreSQL extends the Storage Manager API enabling to integrate custom storage managers.
 
 ## Features
 
 The following table provides the differences between the builds:
 
-| PostgreSQL Community build  | Percona Server for PostgreSQL build <br> (in addition to features included in the PostgreSQL Community build)|
+| PostgreSQL Community build  | Percona Server for PostgreSQL build <br> |
 |----------------------|-------------------------------|
-| Table encryption: <br> - data tables, <br> - TOAST tables <br> - temporary tables created during the database operation.<br><br> Metadata of those tables is not encrypted. | Index data encryption for encrypted tables |
+| Table encryption: <br> - data tables, <br> - TOAST tables <br> - temporary tables created during the database operation.<br><br> Metadata of those tables is not encrypted. | Table encryption: <br> - data tables, <br> - TOAST tables <br> - temporary tables created during the database operation.<br> - Index data for encrypted tables<br><br> Metadata of those tables is not encrypted.  |
 | Write-Ahead Log (WAL) encryption of data in encrypted tables | Write-Ahead Log (WAL) encryption of data for encrypted and non-encrypted tables  |
-| Multi-tenancy support|  |   
-| Table-level granularity | | 
-| Key management via: <br> - HashiCorp Vault; <br> - Local keyfile | 
+| Multi-tenancy support| Multi-tenancy support |
+| Table-level granularity |Table-level granularity | 
+| Key management via: <br> - HashiCorp Vault; <br> - Local keyfile | Key management via: <br> - HashiCorp Vault; <br> - Local keyfile|
+| | Logical replication of encrypted tables | 
 
 ## Future releases
 
 The following is planned for future releases of `pg_tde`:
 
-* Logical replication support
 * KMIP integration for key management
+* Global principal keys 
 
-<i warning>:material-alert: Warning:</i> Note that introducing encryption/decryption affects performance. Our benchmark tests show less than 10% performance overhead for most situations. However, in some specific applications such as those using JSONB operations, performance degradation might be higher.
 
 [Get started](install.md){.md-button}

documentation/docs/index.md

@@ -10,7 +10,7 @@
 
  `pg_tde` is provided in database specific builds for:
 
-* [Percona Server for PostgreSQL 17](https://docs.percona.com/postgresql/17/) as part of Percona Distribution for PostgreSQL 17. This build includes all capabilities and features of `pg_tde`
+* [Percona Server for PostgreSQL 17](https://docs.percona.com/postgresql/17/postgresql-server.html) as part of Percona Distribution for PostgreSQL 17. This build includes all capabilities and features of `pg_tde`
 * PostgreSQL Community 16.x, PostgreSQL Community 17.0 and Percona Distribution for PostgreSQL 16.0. This build provides limited capabilities. Namely, index level encryption is not supported as it requires the use of a custom storage manager.
 
 [Compare builds](features.md){.md-button}

documentation/mkdocs.yml

@@ -155,7 +155,8 @@ extra:
 
 nav:
   - Home: index.md
-  - tde.md
+  - tde.md 
+  - features.md
   - Get started:
     - "Install": "install.md"
     - "Via apt": apt.md