Docs bug fixed

NordicSemiconductor · Nov 1, 2018 · 7ae99fe · 7ae99fe
1 parent a9f1a7f
commit 7ae99fe
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/documentation/Automated tests/README.md b/documentation/Automated tests/README.md
@@ -301,19 +301,19 @@ The instance-id attributes are optional and set to 0 by default.
 Reliable Write is described in Bluetooth Core Specification v5.0, Vol 3, Part G, chapter 4.9.5. In order to start the sup-procedure (supported from Android 4.3 and nRF Connect 4.21.0), use:
 
 ```xml
-<begin-reliable-writer [description="DESCRIPTION"] />
+<begin-reliable-write [description="DESCRIPTION"] />
 ```
 
 All following write requests will use Prepare Write, instead of Write procedure. The target device will reply received data back to the Android for verification. If received data is different than the one sent, an assert error will be reported. Multiple characteristics may be written multiple times during a single Reliable Write operation. Other operations may also be performed while ongoing reliable write. However, at least one Write operation must be performed before executing or aborting the Reliable Write sub-procedure.
 
 When all data are sent and verified, use:
 
 ```xml
-<execute-reliable-writer [description="DESCRIPTION"] [timeout="NUMBER"] [target="TARGET_ID"] [expected="SUCCESS"] />
+<execute-reliable-write [description="DESCRIPTION"] [timeout="NUMBER"] [target="TARGET_ID"] [expected="SUCCESS"] />
 ```
 or
 ```xml
-<abort-reliable-writer [description="DESCRIPTION"] [timeout="NUMBER"] [target="TARGET_ID"] [expected="SUCCESS"] />
+<abort-reliable-write [description="DESCRIPTION"] [timeout="NUMBER"] [target="TARGET_ID"] [expected="SUCCESS"] />
 ```
 to revert to a state from before the sub-procedure was started.