Merge pull request #311492 from christinechen2/docs-editor/storage-redundancy-change-faq-1770399354

Update storage-redundancy-change-faq.md

Author: prmerger-automator[bot]

articles/storage/common/storage-redundancy-change-faq.md

@@ -181,7 +181,6 @@ Zonal conversions involve adding or removing availability zone options to your a
 
 - **Object Replication:** Zonal conversions on accounts with object replication (OR) might generate an error. In this case, you can delete your account's OR policies and attempt the conversion again.
 - **NFSv3:** NFSv3 can't be unconfigured. To convert an NFSv3-enabled account to ZRS, you need to perform a *manual migration*. Manual migrations utilize a feature or tool such as AzCopy to migrate the data of your current storage account to a different storage account with the desired redundancy. To learn more about using AzCopy, see [Use AzCopy to copy blobs](storage-use-azcopy-blobs-copy.md).
-- **Point in time restore (PITR):** Zonal conversions on accounts with point-in-time restore (PITR) might generate an error. In this case, you can disable PITR and retry the migration.
 - **Archive data:** Accounts containing data within the archive tier can generate errors. Before converting, you should rehydrate archive data to either the cold, cool, or hot tier, and then retry your conversion. You can also delete any archived data before converting.
 - **NFSv4 accounts with public endpoints:** You might encounter issues when attempting to migrate a storage account with a public endpoint. You should disable access to the storage account's public endpoints before retrying your conversion. You can read more about changing account replication in the [Change how a storage account is replicated](redundancy-migration.md) article.
 - **Routing choice, internet Routing:** You should set your routing preference to *Microsoft network routing*. For details, see [Configure network routing preference](configure-network-routing-preference.md).