Diff: internal/iothub_client_ll_uploadtoblob.h

Revision:

92:97148cf9aa2a

Parent:

88:248736be106e

--- a/internal/iothub_client_ll_uploadtoblob.h	Thu Jul 12 18:09:13 2018 -0700
+++ b/internal/iothub_client_ll_uploadtoblob.h	Tue Sep 11 11:13:11 2018 -0700
@@ -2,22 +2,22 @@
 // Licensed under the MIT license. See LICENSE file in the project root for full license information.
 
 /** @file iothub_client_ll.h
-*	@brief	 APIs that allow a user (usually a device) to communicate
-*		     with an Azure IoTHub.
+*    @brief     APIs that allow a user (usually a device) to communicate
+*             with an Azure IoTHub.
 *
-*	@details IoTHubClient_LL is a module that allows a user (usually a
-*			 device) to communicate with an Azure IoTHub. It can send events
-*			 and receive messages. At any given moment in time there can only
-*			 be at most 1 message callback function.
+*    @details IoTHubClient_LL is a module that allows a user (usually a
+*             device) to communicate with an Azure IoTHub. It can send events
+*             and receive messages. At any given moment in time there can only
+*             be at most 1 message callback function.
 *
-*			 This API surface contains a set of APIs that allows the user to
-*			 interact with the lower layer portion of the IoTHubClient. These APIs
-*			 contain @c _LL_ in their name, but retain the same functionality like the
-*			 @c IoTHubClient_... APIs, with one difference. If the @c _LL_ APIs are
-*			 used then the user is responsible for scheduling when the actual work done
-*			 by the IoTHubClient happens (when the data is sent/received on/from the wire).
-*			 This is useful for constrained devices where spinning a separate thread is
-*			 often not desired.
+*             This API surface contains a set of APIs that allows the user to
+*             interact with the lower layer portion of the IoTHubClient. These APIs
+*             contain @c _LL_ in their name, but retain the same functionality like the
+*             @c IoTHubClient_... APIs, with one difference. If the @c _LL_ APIs are
+*             used then the user is responsible for scheduling when the actual work done
+*             by the IoTHubClient happens (when the data is sent/received on/from the wire).
+*             This is useful for constrained devices where spinning a separate thread is
+*             often not desired.
 */
 
 #ifndef DONT_USE_UPLOADTOBLOB