Cleared confusion

Author: krofax

pages/builders/app-developers/bridging/standard-bridge.mdx

@@ -239,13 +239,12 @@ The address of this entry is the address of the bridged representation of the to
 
 ## Special considerations
 
-### USDC
+### USDC on OP Mainnet
 
-[Circle](https://www.circle.com/en/), the issuer of [USDC](https://www.circle.com/en/usdc?gad_source=1), natively issues USDC on OP Mainnet [as of September 2023](https://www.circle.com/blog/what-you-need-to-know-native-usdc-on-op-mainnet).
-Before this service was made available, USDC had to be bridged to OP Mainnet via the Standard Bridge.
-This bridged representation of USDC is referred to as `USDC.e`.
-
-Circle recommends that users and developers make use of the native version of USDC issued by Circle over the bridged `USDC.e` token.  Please note that the bridged `USDC.e` token will be deprecated in the near future.
+<Callout type="warning">
+The legacy bridged version of USDC (USDC.e) at address `0x7f5c764cbc14f9669b88837ca1490cca17c31607` is being deprecated on OP Mainnet. 
+Users and developers should migrate to using the native USDC token issued directly by [Circle](https://www.circle.com/en/), the issuer of [USDC](https://www.circle.com/en/usdc?gad_source=1).
+</Callout>
 
 Information about the bridged `USDC.e` token and native USDC token can be found below.