Description of problem:

Remove the Subscriptions tab and Auto-Attach details/steps/ private notes about SCA disabled mentioned under Configuring virtual machine subscriptions ( Chapter 2. Creating an activation key for virtual machines ) Satellite 6.16 documentation

Below steps/details should be removed/updated since  Satellite versions 6.16 (and future versions) will only support Simple Content Access

UNDER Chapter 2. Creating an activation key for virtual machines 

A) Use this procedure to create an activation key with auto-attach enabled and no subscriptions attached. When you register virtual machines using this activation key, the virtual machines inherit a subscription from their hypervisor if that hypervisor has a host-based subscription attached.

B) Private Notes should be removed:

 
This procedure is only valid if you have Simple Content Access (SCA) disabled on Satellite. You are not required to attach subscriptions to Activation Keys if you have SCA enabled. Note that SCA is enabled by default for newly created organizations. To learn more about SCA, see Simple Content Access.

C)

1. Click the Subscriptions tab.
2. Ensure that Auto-Attach is set to Yes. If it is not, click the edit icon, select the check box, and click Save.

Do not add any subscriptions to this activation key.

UNDER Chapter 6. Registering virtual machines to use a host-based subscription 

A) 

Use an auto-attach activation key to register virtual machines so that they inherit a subscription from their hypervisor.

B) 

Prerequisites

• Create an activation key with auto-attach enabled and no subscriptions attached.
• Attach a host-based subscription to the virtual machine’s hypervisor.
• Create and deploy a virt-who configuration that queries the virtual machine’s hypervisor.

C)

Procedure

1. Configure the virtual machine to register with Satellite Server:
2. yum install http://_satellite.example.com_/pub/katello-ca-consumer-latest.noarch.rpm

Also , Please make necessary updates related to registration steps mentioned on 
5.3. Deploying a virt-who configuration on a separate Red Hat Enterprise Linux server 
User Experience & Workflow

The presence of those steps would rather end-up confusing the end-users instead of making it easier for them to navigate through the doc.

Requirements

Please remove the Subscriptions tab and Auto-Attach details/steps/ private notes about SCA disabled mentioned under Configuring virtual machine subscriptions ( Chapter 2. Creating an activation key for virtual machines ) Satellite 6.16 documentation to only  SCA-specific instructions or remove the "auto-attach"  specific commands and private note mentioning about SCA disabled.

Business Impact

 Documentation steps should be aligned with what we have publicly announced via https://access.redhat.com/articles/transition_of_subscription_services_to_the_hybrid_cloud_console