Update note

Author: rchinn1

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -16,7 +16,8 @@ Authentication uses HTTP Basic Auth, which involves a `username:password` that i
 
 In practice that means taking a Segment source **Write Key**,`'abc123'`, as the username, adding a colon, and then the password field is left empty. After base64 encoding `'abc123:'` becomes `'YWJjMTIzOg=='`; and this is passed in the authorization header like so: `'Authorization: Basic YWJjMTIzOg=='`.
 
-**Note:** Encoding the write key without a colon may work due to backward compatibility, but this may not always be the case, so it's important to include the colon before encoding.
+> info ""
+> Include a colon before encoding. While encoding the write key without a colon might work due to backward compatibility, this won't always be the case.  
 
 ### Content-Type
 
@@ -40,7 +41,7 @@ Segment welcomes feedback on API responses and error messages. [Reach out to sup
 Segment recommends you to not exceed 20,000 requests per second with the HTTP API. For [`batch` requests](#batch), there's a limit of 500 KB per request. 
 
 > warning "Engage rate limit"
-> Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more.
+> Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more. 
 
 ## Max request size