Improved readability

Author: nastena1606

contrib/pg_tde/documentation/docs/architecture.md

@@ -77,17 +77,17 @@ HashiCorp Vault can also act as the KMIP server, managing cryptographic keys for
 
 Here’s how encryption of data files works:
 
-First, data files are encrypted with internal keys. Each file that has a different OID, has an internal key. For example, a table with 4 indexes will have 5 internal keys - one for the table and one for each index.	
+First, data files are encrypted with internal keys. Each file that has a different [Object Identifier (OID)](https://www.postgresql.org/docs/current/datatype-oid.html) has an internal key. For example, a table with 4 indexes will have 5 internal keys - one for the table and one for each index.	
 
-The initial decision on what file to encrypt is based on the table access method in PostgreSQL. When you run a `CREATE` or `ALTER TABLE` statement with the `USING tde_heap` clause, the newly created data files are marked as encrypted, and then file operations encrypt/decrypt the data. Later, if an initial file is re-created as a result of a `TRUNCATE` or `VACUUM FULL` command, the newly created file inherits the encryption information and is either encrypted or not. 
+The initial decision on what file to encrypt is based on the table access method in PostgreSQL. When you run a `CREATE` or `ALTER TABLE` statement with the `USING tde_heap` clause, the newly created data files are marked as encrypted, and then file operations encrypt or decrypt the data. Later, if an initial file is re-created as a result of a `TRUNCATE` or `VACUUM FULL` command, the newly created file inherits the encryption information and is either encrypted or not. 
 
 The principal key is used to encrypt the internal keys. The principal key is stored in the key management store. When you query the table, the principal key is retrieved from the key store to decrypt the table. Then the internal key for that table is used to decrypt the data.
 
 WAL encryption is done globally for the entire database cluster. All modifications to any database within a PostgreSQL cluster are written to the same WAL to maintain data consistency and integrity and ensure that PostgreSQL cluster can be restored to a consistent state. Therefore, WAL is encrypted globally. 
 
 When you turn on WAL encryption, `pg_tde` encrypts entire WAL files starting from the first WAL write after the server was started with the encryption turned on.
 
-The same 2-tier approach is used with WAL as with the table data: WAL pages are first encrypted with the internal key. Then the internal key is encrypted with the global principal key.
+The same 2-key approach is used with WAL as with the table data: WAL pages are first encrypted with the internal key. Then the internal key is encrypted with the global principal key.
 
 You can turn WAL encryption on and off so WAL can contain both encrypted and unencrypted data. The WAL encryption GUC variable influences only writes.
 

contrib/pg_tde/documentation/docs/faq.md

@@ -264,7 +264,7 @@ You can also verify if the table in a custom schema is encrypted. Pass the schem
 SELECT pg_tde_is_encrypted('schema.table_name');
 ```
 
-This can additoonally be used the verify that indexes and sequences are encrypted.
+This can additionally be used the verify that indexes and sequences are encrypted.
 
 ### pg_tde_principal_key_info
 

contrib/pg_tde/documentation/docs/functions.md

@@ -2,7 +2,7 @@
 
 `pg_tde` is the open source PostgreSQL extension that provides Transparent Data Encryption (TDE) to protect data at rest. This ensures that the data stored on disk is encrypted, and no one can read it without the proper encryption keys, even if they gain access to the physical storage media. 
 
-Learn more [what is Transparent Data Encryption](tde.md#how-does-it-work) and [why you need it](tde.md#why-do-you-need-tde).
+Learn more [what Transparent Data Encryption is](tde.md#how-does-it-work) and [why you need it](tde.md#why-do-you-need-tde).
 
 !!! important 
 

contrib/pg_tde/documentation/docs/index.md

@@ -21,13 +21,13 @@ Install `pg_tde` using one of the available installation methods:
 
     `pg_tde` is a part of the Percona Distribution for PostgreSQL Docker image. Use this image to enjoy full encryption capabilities. Check below to get access to a detailed step-by-step guide. 
 
-    [Run in Docker :material-arrow-right:](https://docs.percona.com/postgresql/latest/docker.html)
+    [Run in Docker :material-arrow-right:](https://docs.percona.com/postgresql/latest/docker.html){.md-button}
 
 === ":octicons-download-16: Manual download"
 
     `pg_tde` is included in the Percona Distribution for PostgreSQL tarball. Check below to get access to a detailed step-by-step guide. 
 
-    [Install from tarballs](https://docs.percona.com/postgresql/17/tarball.html) guide for instructions.
+    [Install from tarballs :material-arrow-right:](https://docs.percona.com/postgresql/17/tarball.html){.md-button}
 
 
 ## Next steps

contrib/pg_tde/documentation/docs/install.md

@@ -52,6 +52,7 @@ theme:
     - content.tabs.link
     - navigation.top
     - navigation.tracking
+    - navigation.indexes
 
 
 
@@ -92,8 +93,6 @@ markdown_extensions:
       linenums: false
   - pymdownx.snippets:
       base_path: ["snippets"]
-#      auto_append:
-#        - services-banner.md
   - pymdownx.emoji:
       emoji_index: !!python/name:material.extensions.emoji.twemoji
       emoji_generator: !!python/name:material.extensions.emoji.to_svg
@@ -169,6 +168,7 @@ nav:
   - Concepts:
     - "What is TDE": tde.md
     - table-access-method.md
+  - architecture.md
   - How to:
     - Set up multi-tenancy: multi-tenant-setup.md
     - Use reference to external parameters: external-parameters.md