From 4bbdf40dd0b83c12dbb184120448b5ede0771ea8 Mon Sep 17 00:00:00 2001 From: Annie_wang Date: Mon, 13 Jun 2022 20:34:41 +0800 Subject: [PATCH] update docs Signed-off-by: Annie_wang --- en/device-dev/driver/driver-platform-i2c-des.md | 2 +- .../guide/device-camera-control-demo-photoguide.md | 8 ++++---- .../guide/device-iotcamera-control-demo-photodevguide.md | 8 ++++---- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/en/device-dev/driver/driver-platform-i2c-des.md b/en/device-dev/driver/driver-platform-i2c-des.md index be20c1bf72..0cd8cc6526 100644 --- a/en/device-dev/driver/driver-platform-i2c-des.md +++ b/en/device-dev/driver/driver-platform-i2c-des.md @@ -4,7 +4,7 @@ The Inter-Integrated Circuit \(I2C\) is a simple, bidirectional, and synchronous serial bus that uses merely two wires. -In an I2C communication, one controller communicates with one or more devices through the serial data line \(SDA\) and serial clock line \(SCL\), as shown in [Figure 1](#fig1135561232714). +In an I2C communication, one controller communicates with one or more devices through the serial data line \(SDA\) and serial clock line \(SCL\), as shown in the figure below. I2C data transfer must begin with a **START** condition and end with a **STOP** condition. Data is transmitted byte-by-byte from the most significant bit to the least significant bit. diff --git a/en/device-dev/guide/device-camera-control-demo-photoguide.md b/en/device-dev/guide/device-camera-control-demo-photoguide.md index de61ed05e5..1a26e078d9 100644 --- a/en/device-dev/guide/device-camera-control-demo-photoguide.md +++ b/en/device-dev/guide/device-camera-control-demo-photoguide.md @@ -250,7 +250,7 @@ None ## How to Develop -1. Extend the **CameraDeviceCallback** class and call **OnCameraStatus** to customize operations when the camera device changes, for example, when a camera becomes available or unavailable. +1. Extend the **CameraDeviceCallback** class and call **OnCameraStatus** to customize operations when the camera device changes, for example, when a camera becomes available or unavailable. ``` class SampleCameraDeviceCallback : public CameraDeviceCallback { @@ -261,7 +261,7 @@ None }; ``` -2. Extend the **FrameStateCallback** class. After obtaining the frame data, save the data as a file. +2. Extend the **FrameStateCallback** class. After obtaining the frame data, save the data as a file. ``` static void SampleSaveCapture(const char *p, uint32_t size) @@ -305,7 +305,7 @@ None }; ``` -3. Extend the **CameraStateCallback** class and customize operations when the camera state changes \(configuration successful or failed, and creation successful or failed\). +3. Extend the **CameraStateCallback** class and customize operations when the camera state changes \(configuration successful or failed, and creation successful or failed\). ``` class SampleCameraStateMng : public CameraStateCallback { @@ -358,7 +358,7 @@ None camKit->CreateCamera(camId, CamStateMng, eventHdlr); ``` -6. Based on the callback design in [1](#en-us_topic_0000001052170554_li378084192111), [2](#en-us_topic_0000001052170554_li8716104682913), and [3](#en-us_topic_0000001052170554_li6671035102514), perform related operations until the **OnCreated** callback obtains **cam\_**. +6. Based on the callback design in steps 1 to 3, perform related operations until the **OnCreated** callback obtains **cam\_**. ``` void OnCreated(Camera &c) override diff --git a/en/device-dev/guide/device-iotcamera-control-demo-photodevguide.md b/en/device-dev/guide/device-iotcamera-control-demo-photodevguide.md index c54609ed2c..013f080c0d 100644 --- a/en/device-dev/guide/device-iotcamera-control-demo-photodevguide.md +++ b/en/device-dev/guide/device-iotcamera-control-demo-photodevguide.md @@ -250,7 +250,7 @@ None ## How to Develop -1. Extend the **CameraDeviceCallback** class and call **OnCameraStatus** to customize operations when the camera device changes, for example, when a camera becomes available or unavailable. +1. Extend the **CameraDeviceCallback** class and call **OnCameraStatus** to customize operations when the camera device changes, for example, when a camera becomes available or unavailable. ``` class SampleCameraDeviceCallback : public CameraDeviceCallback { @@ -261,7 +261,7 @@ None }; ``` -2. Extend the **FrameStateCallback** class. After obtaining the frame data, save the data as a file. +2. Extend the **FrameStateCallback** class. After obtaining the frame data, save the data as a file. ``` static void SampleSaveCapture(const char *p, uint32_t size) @@ -305,7 +305,7 @@ None }; ``` -3. Extend the **CameraStateCallback** class and customize operations when the camera state changes \(configuration successful or failed, and creation successful or failed\). +3. Extend the **CameraStateCallback** class and customize operations when the camera state changes \(configuration successful or failed, and creation successful or failed\). ``` class SampleCameraStateMng : public CameraStateCallback { @@ -358,7 +358,7 @@ None camKit->CreateCamera(camId, CamStateMng, eventHdlr); ``` -6. Based on the callback design in [1](#en-us_topic_0000001052170554_li378084192111), [2](#en-us_topic_0000001052170554_li8716104682913), and [3](#en-us_topic_0000001052170554_li6671035102514), perform related operations until the **OnCreated** callback obtains **cam\_**. +6. Based on the callback design in steps 1 to 3, perform related operations until the **OnCreated** callback obtains **cam\_**. ``` void OnCreated(Camera &c) override -- GitLab