feat: small formatting changes

Author: ADubhlaoich

content/waf/tools/compiler.md

@@ -12,17 +12,9 @@ nd-content-type: how-to
 nd-product: NAP-WAF
 ---
 
-{{< call-out "warning" "Information architecture note" >}}
-
-This page replaces [V5 F5 WAF for NGINX Compiler]({{< ref "/nap-waf/v5/admin-guide/compiler.md">}}) page.
-
-Does this exclusively work with V5 versions?
-
-{{</ call-out>}}
-
 This document describes how to use the F5 WAF for NGINX compiler, a tool for converting security policies and logging profiles from JSON to a bundle file that F5 WAF can process and apply.
 
-You can use it to get the latest security updates for Attack Signatures, Threat Campaigns and Bot Signatures. The compiler is packaged as a Docker image and can executed using the Docker CLI or as part of a continuous integration/ continuous delivery (CI/CD) pipeline.
+You can use it to get the latest security updates for Attack Signatures, Threat Campaigns and Bot Signatures. The compiler is packaged as a Docker image and can executed using the Docker CLI or as part of a continuous integration/continuous delivery (CI/CD) pipeline.
 
 One or more bundle files can be referenced in the NGINX configuration file, and you can configure global settings such as the cookie seed and user-defined signatures.
 
@@ -230,15 +222,15 @@ The global settings allows configuration of the following items:
 
 ### cookie-protection
 
-| Field Name | Reference | Type | Description |
-| ---------- | --------- | ---- | ----------- |
-| seed | string | The seed value is used by F5 WAF for NGINX to generate the encryption key for the cookies it creates. These cookies are used for various purposes such as validating the integrity of the cookies generated by the application. Use a random alphanumeric string of at least 20 characters length (but not more than 1000 characters). |
+| Name       | Type   | Description |
+| ---------- | ------ | ----------- |
+| seed       | string | The seed value is used by F5 WAF for NGINX to generate the encryption key for the cookies it creates. These cookies are used for various purposes such as validating the integrity of the cookies generated by the application. Use a random alphanumeric string of at least 20 characters length (but not more than 1000 characters). |
 
 ### user-defined-signatures
 
-| Field Name | Reference | Type | Description |
-| ---------- | --------- | ---- | ----------- |
-| $ref | Yes | string | Path to the file that contains the user defined signatures. |
+| Name  | Reference | Type   | Description |
+| ----- | --------- | ------ | ----------- |
+| $ref  | Yes       | string | Path to the file that contains the user defined signatures. |
 
 #### Example