Update CN trans for timers.rst and ota.rst

docs/en/api-reference/peripherals/timer.rst

@@ -92,6 +92,7 @@ Interrupts
 ^^^^^^^^^^
 
 Registration of an interrupt callback for a specific timer can be done by calling :cpp:func:`timer_isr_callback_add` and passing in the group ID, timer ID, callback handler and user data. The callback handler will be invoked in ISR context, so user shouldn't put any blocking API in the callback function.
+
 The benefit of using interrupt callback instead of precessing interrupt from scratch is, you don't have to deal with interrupt status check and clean stuffs, they are all addressed before the callback got run in driver's default interrupt handler.
 
 For more information on how to use interrupts, please see the application example below.

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

@@ -170,8 +170,7 @@ Restrictions:
     :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``.
+    - Factory and Test partitions are not supported in anti rollback scheme and hence partition table should not have partition with SubType set to ``factory`` or ``test``.
 
 ``security_version``: