docs:change tarball extension from tgz to tar.gz

Author: Dindihub

content/controller/admin-guides/backup-restore/backup-restore-cluster-config.md

@@ -19,7 +19,7 @@ After installing F5 NGINX Controller, you should back up the cluster config and
   /opt/nginx-controller/helper.sh cluster-config save
   ```
 
-  The file is saved to `/opt/nginx-controller/cluster-config.tgz`.
+  The file is saved to `/opt/nginx-controller/cluster-config.tar.gz`.
 
 - To restore the cluster's config and encryption keys, take the following steps:
 

content/controller/admin-guides/install/install-nginx-controller.md

@@ -325,7 +325,7 @@ After installing NGINX Controller, you should back up the cluster config and enc
   /opt/nginx-controller/helper.sh cluster-config save
   ```
 
-  The file is saved to `/opt/nginx-controller/cluster-config.tgz`.
+  The file is saved to `/opt/nginx-controller/cluster-config.tar.gz`.
 
 - To restore the cluster's config and encryption keys, take the following steps:
 

content/controller/admin-guides/install/using-helper-script.md

@@ -84,7 +84,7 @@ After installing NGINX Controller, you should back up the cluster config and enc
   /opt/nginx-controller/helper.sh cluster-config save
   ```
 
-  The file is saved to `/opt/nginx-controller/cluster-config.tgz`.
+  The file is saved to `/opt/nginx-controller/cluster-config.tar.gz`.
 
 - To restore the cluster's config and encryption keys, take the following steps:
 

content/includes/nap-waf/bundles-volume-mount.md

@@ -22,6 +22,6 @@ By setting up this volume mount, the bundle files can be referenced within your
 For instance:
 
    ```nginx
-   app_protect_policy_file /bundles/custom_policy.tgz;
-   app_protect_security_log /bundles/custom_logging_profile.tgz syslog:server=localhost:514;
+   app_protect_policy_file /bundles/custom_policy.tar.gz;
+   app_protect_security_log /bundles/custom_logging_profile.tar.gz syslog:server=localhost:514;
    ```

content/includes/nap-waf/concept/grpc-logging.md

@@ -14,9 +14,9 @@ server {
     server_name my_grpc_service.com;
     location / {
         app_protect_enable on;
-        app_protect_policy_file "/etc/app_protect/conf/policy_with_grpc_profile.tgz";
+        app_protect_policy_file "/etc/app_protect/conf/policy_with_grpc_profile.tar.gz";
         app_protect_security_log_enable on;
-        app_protect_security_log "/etc/app_protect/conf/log_grpc_all.tgz" stderr;
+        app_protect_security_log "/etc/app_protect/conf/log_grpc_all.tar.gz" stderr;
         grpc_pass grpcs://grpc_backend;
     }
 }

content/includes/nap-waf/config/common/grpc-content-profiles.md

@@ -94,12 +94,12 @@ The profile in this example enables checking of attack signatures and disallowed
 
 The main IDL file, `album.proto` is marked as `primary`. The file it imports, `messages.proto`, is marked as secondary, i.e., `isPrimary` is `false` and so should be any imported file. In order for App Protect to be able to match it to the import statement, the file location should be specified as done in the example above using the `importUrl` property.
 
-An alternative and probably more convenient way to specify all the IDL files, the primary and all its imports, direct and indirect, is to bundle them into a single tar file in the same directory structure as they are expected by the import statements. In this case, you will have to specify which of the files in the tarball is the primary one. The supported formats are `tar` and `tgz`. App Protect will identify the file type automatically (tar, gzipped tar, or JSON) and handle it accordingly. Following the above example:
+An alternative and probably more convenient way to specify all the IDL files, the primary and all its imports, direct and indirect, is to bundle them into a single tar file in the same directory structure as they are expected by the import statements. In this case, you will have to specify which of the files in the tarball is the primary one. The supported formats are `tar` and `tar.gz`. App Protect will identify the file type automatically (tar, gzipped tar, or JSON) and handle it accordingly. Following the above example:
 
 ```json
 "idlFiles": [{
     "idlFile": {
-        "$ref": "file:///grpc_files/album_service_files.tgz"
+        "$ref": "file:///grpc_files/album_service_files.tar.gz"
     },
     "primaryIdlFileName": "album_service.proto"
 }]

content/includes/nap-waf/nap-k8s-use-compiled-bundles.md

@@ -1,7 +1,7 @@
 In this setup, copy your compiled policy and logging profile bundles to `/mnt/nap5_bundles_pv_data` on a cluster node. Make sure that input files are accessible to UID 101. Then, in your NGINX configuration, refer to these files from `/etc/app_protect/bundles`.
 
-For example, to apply `custom_policy.tgz` that you've placed in `/mnt/nap5_bundles_pv_data/`, use:
+For example, to apply `custom_policy.tar.gz` that you've placed in `/mnt/nap5_bundles_pv_data/`, use:
 
 ```nginx
-app_protect_policy_file "/etc/app_protect/bundles/custom_policy.tgz";
+app_protect_policy_file "/etc/app_protect/bundles/custom_policy.tar.gz";
 ```

content/nap-dos/troubleshooting-guide/how-to-troubleshoot.md

@@ -150,7 +150,7 @@ If there are any problems, collect the troubleshooting information in a tarball
 3. Create the tarball:
 
    ```shell
-   tar cvfz logs.tgz `cat logs.txt`
+   tar cvfz logs.tar.gz `cat logs.txt`
    ```
 
-4. Send `logs.tgz` to your customer support.
+4. Send `logs.tar.gz` to your customer support.

content/nap-waf/v4/admin-guide/upgrade-nap-waf.md

@@ -22,7 +22,7 @@ For details on matching NGINX App Protect WAF releases with their WAF compiler v
 
 ## Upgrade NGINX App Protect on the Data Plane
 
-Before you start, make sure you're using NGINX Management Suite for your policy management. Your NGINX configuration should be set up to use WAF policies with a _.tgz_ extension.
+Before you start, make sure you're using NGINX Management Suite for your policy management. Your NGINX configuration should be set up to use WAF policies with a _.tar.gz_ extension.
 
 To update NGINX App Protect on an NGINX data plane instance, follow these steps:
 

content/nap-waf/v4/troubleshooting-guide/troubleshooting.md

@@ -105,9 +105,9 @@ In order to open a support ticket, collect the troubleshooting information in a
  5. Create the tarball:
 
      ```none
-     tar cvfz logs.tgz `cat logs.txt`
+     tar cvfz logs.tar.gz `cat logs.txt`
      ```
 
- 7. Attach `logs.tgz` to support ticket.
+ 7. Attach `logs.tar.gz` to support ticket.
 
  8. On the support ticket, in the NGINX App Protect WAF, set the release version according to the `opt/app_protect/RELEASE` file.