Thanks for your feedback on documentation. We will consider improving it.
Since your issue is resolved, it would be helpful if you post the solution on Github also and close the issue.

This patch is just a simple way to verify that ESP_GATTC_READ_CHAR_EVT event is triggered when esp_ble_gattc_read_char function is called. Since the default behavior of gatt_client is to write and not to read server's characteristic, I called read_char inside write_char and inserted logs to verify t...

Hello Susan,

As far as I have understood your issue, I have provided a patch to reproduce it by running gatt_server and gatt_client examples of esp-idf at master. After applying this patch ESP_GATTC_READ_CHAR_EVT is getting triggered after esp_ble_gattc_read_char is being called.