From 08ce9d9751eb5e183b6deefab48fb9eabffa4f38 Mon Sep 17 00:00:00 2001 From: Prakhar Maurya <53076720+prakharmaurya@users.noreply.github.com> Date: Mon, 3 Apr 2023 18:10:28 +0530 Subject: [PATCH] fic: extra can removed --- docs/en/api-reference/api-conventions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/api-reference/api-conventions.rst b/docs/en/api-reference/api-conventions.rst index 008dcf84d7..98ad98fa7c 100644 --- a/docs/en/api-reference/api-conventions.rst +++ b/docs/en/api-reference/api-conventions.rst @@ -9,7 +9,7 @@ ESP-IDF provides several kinds of programming interfaces: * C functions, structures, enums, type definitions and preprocessor macros declared in public header files of ESP-IDF components. Various pages in the API Reference section of the programming guide contain descriptions of these functions, structures and types. * Build system functions, predefined variables and options. These are documented in the :ref:`build system guide`. -* :doc:`Kconfig ` options can can be used in code and in the build system (CMakeLists.txt) files. +* :doc:`Kconfig ` options can be used in code and in the build system (CMakeLists.txt) files. * :doc:`Host tools <../api-guides/tools/index>` and their command line parameters are also part of ESP-IDF interface. ESP-IDF consists of components written specifically for ESP-IDF as well as third-party libraries. In some cases, an ESP-IDF-specific wrapper is added to the third-party library, providing an interface that is either simpler or better integrated with the rest of ESP-IDF facilities. In other cases, the original API of the third-party library is presented to the application developers.