Renamed RHTAP to RHADS

[gtrivedi88]

MPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):
main, 1.6.x
Issue:
HACDOCS-1364

[rhdh-bot]

Preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1233/

[Gerry-Forde]

@gtrivedi88 Is Red Hat Advanced Developer Suite - secure supply chain the approved product name?

It just looks a little strange when it's read in the docs as "RHADS - ssc includes tools like Red Hat Trusted Artifact Signer..."

Would Red Hat Advanced Developer Suite - Secure Supply Chain (RHADS - SSC) read better e.g. "RHADS - SSC includes tools like Red Hat Trusted Artifact Signer..."

Maybe this has been clarified by you already?

[gtrivedi88]

yes, that's approved
https://docs.google.com/document/d/14UbzGr8Rg_2SI83JOIQcLMLX0UOjUud8FsGfEsa8uJ8/edit?tab=t.0

[Gerry-Forde]

/lgtm

[Gerry-Forde]

/cherry-pick release-1.6

[openshift-cherrypick-robot]

@Gerry-Forde: #1233 failed to apply on top of branch "release-1.6":

Applying: Renamed RHTAP to RHADS
.git/rebase-apply/patch:45: trailing whitespace.
{rhads-very-short} includes tools like {rhtas-brand-name} ({rhtas-very-short}) for code integrity, {rhtpa-brand-name} ({rhtpa-very-short}) for automated Software build of Materials (SBOM) creation, and {rhacs-brand-name} ({rhacs-very-short}) for vulnerability scanning. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	artifacts/attributes.adoc
Falling back to patching base and 3-way merge...
Auto-merging artifacts/attributes.adoc
CONFLICT (content): Merge conflict in artifacts/attributes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Renamed RHTAP to RHADS

In response to this:

/cherry-pick release-1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.