Change NGINX App Protect WAF name to reflect new branding

[ADubhlaoich]

Overview

As a user, I want consistent product names, So I can understand what instructions are intended for.

Description

NGINX App Protect WAF's name will be simplified to NGINX WAF. As part of the refactor effort, this change should be reflected when moving and updating content.

This update will also need to be applied to any documentation that refers to the product outside of its own documentation set, such as other products it integrates with like NGINX Ingress Controller and NGINX One Console.

Tasks

• Update any existing, non-evergreen content¹ to use NGINX WAF
• Update any process documentation (such as the style guide) to refer to NGINX WAF

Acceptance criteria

• As a user, I see the name NGINX WAF when exploring content for or mentioning the product

Footnotes

1. In context, evergreen content would be reference content such as changelogs for older versions in which updating the product name could cause confusion. ↩