doc: connectivity: bluetooth: sync function name
sync function name `bt_conn_le_create` with the code. Signed-off-by: Hanf Gai <gaihanfu@live.com>
This commit is contained in:
parent
e40859f787
commit
b8d3e9c50e
2 changed files with 2 additions and 2 deletions
|
@ -22,7 +22,7 @@ define callbacks for connection & disconnection events, as well as other
|
|||
events related to a connection such as a change in the security level or
|
||||
the connection parameters. When acting as a central the application will
|
||||
also get hold of the connection object through the return value of the
|
||||
:c:func:`bt_conn_create_le` API.
|
||||
:c:func:`bt_conn_le_create` API.
|
||||
|
||||
API Reference
|
||||
*************
|
||||
|
|
|
@ -280,7 +280,7 @@ To initially discover a device to connect to the application will likely
|
|||
use the :c:func:`bt_le_scan_start` API, wait for an appropriate device
|
||||
to be found (using the scan callback), stop scanning using
|
||||
:c:func:`bt_le_scan_stop` and then connect to the device using
|
||||
:c:func:`bt_conn_create_le`. If the central wants to keep
|
||||
:c:func:`bt_conn_le_create`. If the central wants to keep
|
||||
automatically reconnecting to the peripheral it should use the
|
||||
:c:func:`bt_le_set_auto_conn` API.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue