docs: ota: fix note about security version efuse size

Author: mahavirj

docs/en/api-reference/system/ota.rst

@@ -165,9 +165,13 @@ If you want to avoid the download/erase overhead in case of the app from the ser
 
 Restrictions:
 
-- The number of bits in the ``secure_version`` field is limited to 32 bits. This means that only 32 times you can do an anti-rollback. You can reduce the length of this efuse field use :ref:`CONFIG_BOOTLOADER_APP_SEC_VER_SIZE_EFUSE_FIELD` option.
-- Anti-rollback only works if the encoding scheme for efuse is set to ``NONE``.
-- The partition table should not have a factory partition, only two of the app.
+.. list::
+
+    :esp32: - The number of bits in the ``secure_version`` field is limited to 32 bits. This means that only 32 times you can do an anti-rollback. You can reduce the length of this efuse field using :ref:`CONFIG_BOOTLOADER_APP_SEC_VER_SIZE_EFUSE_FIELD` option.
+    :not esp32: - The number of bits in the ``secure_version`` field is limited to 16 bits. This means that only 16 times you can do an anti-rollback. You can reduce the length of this efuse field using :ref:`CONFIG_BOOTLOADER_APP_SEC_VER_SIZE_EFUSE_FIELD` option.
+    :esp32: - Anti-rollback works only if the encoding scheme for efuse is set to ``NONE``.
+    - Factory partition is not supported in anti rollback scheme and hence partition table should not have partition with SubType set to ``factory``.
+    - Test partition is not supported in anti rollback scheme and hence partition table should not have partition with SubType set to ``test``.
 
 ``security_version``: