Minor rewording

Author: pwseg

src/connections/sources/catalog/cloud-apps/salesforce/index.md

@@ -118,7 +118,8 @@ When a new Object/Collection is enabled, Segment automatically runs a full histo
 
 However, for custom properties/columns, Segment only populates the custom property with data that comes in after the custom field was enabled. In order to populate the new custom field(s) for records that have previously been synced, you need to initiate a manual re-sync. 
 
-**Note** Initiating a full re-sync might have an impact on your workspace's [API calls + Object](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-is-object-throughput-calculated) usage. 
+> info ""
+> Initiating a full re-sync might impact your workspace's [API calls + Object](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-is-object-throughput-calculated){:target="_blank"} usage. 
 
 For Salesforce, Segment uses the `SystemModstamp`(system_modstamp) field to checkpoint collections that sync incrementally. When enabled, Segment syncs collections incrementally. When disabled, Segment syncs collections fully. If you'd like to force a collection to sync fully on the next run to bring in historical data, you can disable the `SystemModstamp` field on the collection, allow the next sync to complete and then re-enable `SystemModstamp` so the collection syncs incrementally in the coming syncs.