diff --git a/en/device-dev/subsystems/subsys-dfx-hisysevent-logging.md b/en/device-dev/subsystems/subsys-dfx-hisysevent-logging.md
index 23edcbae978020463839ea97b876ef4819fe09d1..2bb67bf541229f541a5461db0c04beecbeabd18e 100644
--- a/en/device-dev/subsystems/subsys-dfx-hisysevent-logging.md
+++ b/en/device-dev/subsystems/subsys-dfx-hisysevent-logging.md
@@ -23,13 +23,14 @@ Use HiSysEvent logging to flush logged event data to disks.
HiSysEvent logging is implemented using the API provided by the **HiSysEvent** class. For details, see the API Reference.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+>
> In OpenHarmony-3.2-Beta3, HiSysEvent logging is open for restricted use to avoid event storms. The **HiSysEvent::Write** API in Table 1 is replaced by the **HiSysEventWrite** API in Table 2. The **HiSysEvent::Write** API has been deprecated. Use the **HiSysEventWrite** API instead for HiSysEvent logging.
**Table 1** C++ event logging API (deprecated)
| API | Description |
| ------------------------------------------------------------ | ---------------------- |
-| template<typename... Types>
static int Write(const std::string &domain, const std::string &eventName, EventType type, Types... keyValues) | Flushes logged event data to disks.|
+| template<typename... Types>
static int Write(const std::string &domain, const std::string &eventName, EventType type, Types... keyValues) | Flushes logged event data to disks.|
**Table 2** C++ event logging API (in use)
| API | Description |
@@ -49,7 +50,7 @@ HiSysEvent logging is implemented using the API provided by the **HiSysEvent** c
The following table describes the kernel event logging APIs.
-**Table 4** Description of kernel event logging APIs
+**Table 4** Kernel event logging APIs
| API | Description |
| ------------------------------------------------------------ | ------------------------------------ |
diff --git a/en/readme/globalization.md b/en/readme/globalization.md
index 8ba91ef0aa3a8cd788fe54792a4a7148af5c3cdf..8e1841cc3fb0c65a43b29fa7c8ac07c4e931a2b8 100755
--- a/en/readme/globalization.md
+++ b/en/readme/globalization.md
@@ -15,7 +15,7 @@ If OpenHarmony devices and applications need to be used globally, they must meet
## Architecture
-**Figure 1** Architecture of the globalization subsystem
+**Figure 1** Architecture of the globalization subsystem
![](figures/architecture-of-the-globalization-subsystem.png "architecture-of-the-globalization-subsystem")