Apply suggestions from code review

Author: stayseesong

src/connections/reverse-etl/index.md

@@ -301,5 +301,5 @@ Column JSON size | The maximum size of any single column value. | 128 KiB
 
 ## FAQs
 
-#### Why do my sync results show "**No records extracted**" when I select "**Updated records**" after I enable the mapping? 
-It's expected when you select **Updated records** and the records did not change after the first sync. During the first sync, the reverse ETL system calculates a snapshot of all the results and creates records in the `_segment_reverse_etl` schema. All the records are considered as *Added records* instead of *Updated records* at this time. The records can only meet the *Updated records* condition when the underlying values change after the first sync completes.
+#### Why do my sync results show *No records extracted* when I select *Updated records* after I enable the mapping? 
+It's expected that when you select **Updated records** the records do not change after the first sync. During the first sync, the reverse ETL system calculates a snapshot of all the results and creates records in the `_segment_reverse_etl` schema. All the records are considered as *Added records* instead of *Updated records* at this time. The records can only meet the *Updated records* condition when the underlying values change after the first sync completes.