Apply suggestions from code review

Co-authored-by: pwseg <[email protected]>

Author: stayseesong

src/connections/destinations/index.md

@@ -223,12 +223,12 @@ The following destinations support bulk batching:
 ### Hashing 
 Segment automatically hashes personally identifiable information (PII). This simplifies implementation for teams with data privacy requirements and eliminates issues with double-hashing that can result in failed matching at destinations. 
 
-These are the 2 types of data that Segment handles for hashing:
+Segment supports these 2 types of data for hashing:
 * **Plain text data:** When you send plain text values to destinations that require hashed values, Segment automatically normalizes and hashes these values. 
 * **Pre-hashed data:** If you already hash your data before sending it to Segment, Segment is able to detect that the data is hashed, and will pass your pre-hashed data directly to the destination, avoiding double-hashing. 
 
 > info ""
-> When pre-hashing data yourself, ensure you follow each destination's specific hashing requirements. Fields that support automatic hashing detection will have a tooltip indicating *"If not hashed, Segment will hash this value."*
+> If you choose to hash data yourself, ensure you follow each destination's specific hashing requirements. Fields that support automatic hashing detection will display a tooltip indicating *"If not hashed, Segment will hash this value."*
 
 For destination-specific hashing requirements, refer to the destination's API documentation.