doc: Update English pages with generic target name

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

@@ -8,7 +8,7 @@ ESP-IDF applications use the common computer architecture patterns of *stack* (d
 
 Because ESP-IDF is a multi-threaded RTOS environment, each RTOS task has its own stack. By default, each of these stacks is allocated from the heap when the task is created. (See :cpp:func:`xTaskCreateStatic` for the alternative where stacks are statically allocated.)
 
-Because ESP32 uses multiple types of RAM, it also contains multiple heaps with different capabilities. A capabilities-based memory allocator allows apps to make heap allocations for different purposes.
+Because {IDF_TARGET_NAME} uses multiple types of RAM, it also contains multiple heaps with different capabilities. A capabilities-based memory allocator allows apps to make heap allocations for different purposes.
 
 For most purposes, the standard libc ``malloc()`` and ``free()`` functions can be used for heap allocation without any special consideration.
 
@@ -18,7 +18,7 @@ capabilities-based heap memory allocator. If you want to have memory with certai
 Memory Capabilities
 -------------------
 
-The ESP32 contains multiple types of RAM:
+The {IDF_TARGET_NAME} contains multiple types of RAM:
 
 - DRAM (Data RAM) is memory used to hold data. This is the most common kind of memory accessed as heap.
 - IRAM (Instruction RAM) usually holds executable data only. If accessed as generic memory, all accesses must be :ref:`32-bit aligned<32-Bit Accessible Memory>`.
@@ -26,7 +26,7 @@ The ESP32 contains multiple types of RAM:
 
 For more details on these internal memory types, see :ref:`memory-layout`.
 
-It's also possible to connect external SPI RAM to the ESP32 - :doc:`external RAM </api-guides/external-ram>` can be integrated into the ESP32's memory map using the flash cache, and accessed similarly to DRAM.
+It's also possible to connect external SPI RAM to the {IDF_TARGET_NAME} - :doc:`external RAM </api-guides/external-ram>` can be integrated into the {IDF_TARGET_NAME}'s memory map using the flash cache, and accessed similarly to DRAM.
 
 DRAM uses capability ``MALLOC_CAP_8BIT`` (accessible in single byte reads and writes). When calling ``malloc()``, the ESP-IDF ``malloc()`` implementation internally calls ``heap_caps_malloc(size, MALLOC_CAP_8BIT)`` in order to allocate DRAM that is byte-addressable. To test the free DRAM heap size at runtime, call cpp:func:`heap_caps_get_free_size(MALLOC_CAP_8BIT)`.
 
@@ -57,7 +57,7 @@ The :ref:`idf.py size <idf.py-size>` command can be used to find the amount of I
 D/IRAM
 ^^^^^^
 
-Some memory in the ESP32 is available as either DRAM or IRAM. If memory is allocated from a D/IRAM region, the free heap size for both types of memory will decrease.
+Some memory in the {IDF_TARGET_NAME} is available as either DRAM or IRAM. If memory is allocated from a D/IRAM region, the free heap size for both types of memory will decrease.
 
 Heap Sizes
 ^^^^^^^^^^
@@ -95,7 +95,7 @@ Use the ``MALLOC_CAP_DMA`` flag to allocate memory which is suitable for use wit
 
 If a certain memory structure is only addressed in 32-bit units, for example an array of ints or pointers, it can be
 useful to allocate it with the ``MALLOC_CAP_32BIT`` flag. This also allows the allocator to give out IRAM memory; something
-which it can't do for a normal malloc() call. This can help to use all the available memory in the ESP32.
+which it can't do for a normal malloc() call. This can help to use all the available memory in the {IDF_TARGET_NAME}.
 
 Memory allocated with ``MALLOC_CAP_32BIT`` can *only* be accessed via 32-bit reads and writes, any other type of access will
 generate a fatal LoadStoreError exception.
@@ -105,7 +105,9 @@ External SPI Memory
 
 When :doc:`external RAM </api-guides/external-ram>` is enabled, external SPI RAM under 4MiB in size can be allocated using standard ``malloc`` calls, or via ``heap_caps_malloc(MALLOC_CAP_SPIRAM)``, depending on configuration. See :ref:`external_ram_config` for more details.
 
-To use the region above the 4MiB limit, you can use the :doc:`himem API</api-reference/system/himem>`.
+..only:: esp32
+
+    To use the region above the 4MiB limit, you can use the :doc:`himem API</api-reference/system/himem>`.
 
 
 API Reference - Heap Allocation