Apply suggestions from code review

Co-authored-by: markzegarelli <[email protected]>
(cherry picked from commit 99b3db9)

Author: stayseesong

src/connections/storage/catalog/db2/index.md

@@ -87,7 +87,7 @@ database shortly.
 If your Db2 Warehouse is in a private network, be sure to [whitelist
 Segment's IP
 address](https://segment.com/docs/connections/storage/warehouses/faq/#which-ips-should-i-whitelist).
-Otherwise, Segment won't be able to load your data.
+Otherwise, Segment can't load your data.
 
 ### Unique User
 

src/connections/storage/catalog/postgres/index.md

@@ -356,7 +356,7 @@ GRANT CREATE, TEMPORARY ON DATABASE <enter database name here> TO segment;
 ## Security
 To make sure your Postgres database is secure:
 - Log in with a user that has read and write permissions so that Segment can write to your database.
-- Whitelist the Segment IP (`52.25.130.38/32`). Otherwise, Segment won't be able to load your data.
+- Whitelist the Segment IP (`52.25.130.38/32`). Otherwise, Segment can't load your data.
 - Create a service user that has `read/write` permissions.
 - Always require SSL/TLS and make sure your data warehouse can only accept secure connections. Segment only connects to your data warehouse using SSL/TLS.
 

src/connections/storage/catalog/redshift/index.md

@@ -70,7 +70,7 @@ After creating a Redshift warehouse, the next step is to connect Segment:
 VPCs keep servers inaccessible to traffic from the internet. With VPC, you're able to designate specific web servers access to your servers.  In this case, you will be whitelisting the [Segment IPs](/docs/connections/storage/warehouses/faq#which-ips-should-i-whitelist) to write to your data warehouse.
 
 ### SSL/TLS
-Always require SSL/TLS and make sure your data warehouse can only accept secure connections. Segment only connects to your data warehouse using SSL/TLS.
+Always require SSL/TLS and make sure your data warehouse accepts only secure connections. Segment only connects to your data warehouse using SSL/TLS.
 
 ## Best practices