Describe the issue:
It seems to me that [1] [2], and [3] are incomplete. They should include instructions on how to scale down and remove the osd post node replacement with the "oc process" command, much like [4], as this step is still necessary in order to get the osd redeployed.

My suggestion is that we keep the information the same in [1], [2] and [3], but add the steps from [4] because they are indeed still needed after the node has been replaced.

Describe the task you were trying to accomplish:

Replace an osd in an Azure environment.

Suggestions for improvement:

Document URL:

[1] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/replacing_devices/dynamically_provisioned_openshift_data_foundation_deployed_on_microsoft_azure

[2] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/replacing_devices/dynamically_provisioned_openshift_data_foundation_deployed_on_google_cloud#replacing-operational-or-failed-storage-devices-on-google-cloud-installer-provisioned-infrastructure_rhodf

[3] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/replacing_devices/dynamically_provisioned_openshift_data_foundation_deployed_on_aws#replacing-operational-or-failed-storage-devices-on-aws-user-provisioned-infrastructure_rhodf

[4] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/replacing_devices/dynamically_provisioned_openshift_data_foundation_deployed_on_vmware

Chapter/Section Number and Title:
Replacing Devices

Dynamically Provisioned Openshift Data Foundation

Environment Details:
ODF on Azure, AWS, and GCP

Any other versions of this document that also needs this update:
N/A

Additional information:
N/A