remove note

core/cap-0067.md

@@ -151,7 +151,7 @@ This section will go over the semantics of how the additional `transfer` events
 
 Note that the `contract` field for these events corresponds to the Stellar Asset Contract address for the respective asset. The Stellar Asset Contract instance is not required to be deployed for the asset. The events will be published using the reserved contract address regardless of deployment status.
 
-The `Address` used on the events specified below will be muxed if the classic operation uses a muxed address. This can be done using the new `SC_ADDRESS_TYPE_MUXED_ACCOUNT` `SCAddressType`. `SC_ADDRESS_TYPE_MUXED_ACCOUNT` will not be used within a `InvokeHostFunctionOp`, but this point can be revisited in the future. If this new `SCAddressType` is used, the type of the underlying `MuxedAccount` must be `KEY_TYPE_MUXED_ED25519` to prevent multiple ways of setting a non-muxed account. (We should discuss this. It probably makes more sense to use a muxed-only type instead).
+The `Address` used on the events specified below will be muxed if the classic operation uses a muxed address. This can be done using the new `SC_ADDRESS_TYPE_MUXED_ACCOUNT` `SCAddressType`. `SC_ADDRESS_TYPE_MUXED_ACCOUNT` will not be used within a `InvokeHostFunctionOp`, but this point can be revisited in the future. If this new `SCAddressType` is used, the type of the underlying `MuxedAccount` must be `KEY_TYPE_MUXED_ED25519` to prevent multiple ways of setting a non-muxed account.
 
 #### Fees paid by source account