* 8. Stop the player <br>
* 9. Destroy a handle <br>
* The TTS API also notifies you (by callback mechanism) when the state of TTS is changed,
- * utterance is started and completed, default voice is changed or an error occured.
+ * utterance is started and completed, default voice is changed or an error occurred.
* An application should register callback functions: tts_state_changed_cb(), tts_utterance_started_cb(),
* tts_utterance_completed_cb(), tts_default_voice_changed_cb(), tts_error_cb(), tts_engine_changed_cb().
*
* The following table shows previous state and post state of main function.
* It can be known what precondition is and which synchronous type is.
* Please check both previous state and post state from the table carefully.
- * In case of tts_prepare() function, state doesn't be changed at once, but acynchronously.
+ * In case of tts_prepare() function, state doesn't be changed at once, but asynchronously.
* From the above state diagram, you can see dotted line as asynchronous api.
* In this case, the state changed callback is only way to know state transition as ready.
* <table>
* It is recommended to design feature related codes in your application for reliability.<br>
* You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.<br>
* To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.<br>
- * More details on featuring your application can be found from <a href="https://developer.tizen.org/development/tools/native-tools/manifest-text-editor#feature"><b>Feature Element</b>.</a>
+ * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
*/