wording and style changes

sade-wusi · web-flow · commit 72ec99b99c41 · 2025-04-23T13:29:52.000+01:00
diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md
@@ -17,7 +17,7 @@ HubSpot is an all-in-one marketing tool that helps attract new leads and convert
 When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your data to [HubSpot's REST API](https://developers.hubspot.com/docs/api/overview){:target="_blank"}.
 
 > warning ""
-> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their base names. HubSpot mandates that custom objects should be referenced by short-hand custom object type name, fullyQualifiedName, or objectTypeId. To avoid issues, ensure the following fields are updated accordingly:
+> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their base names. Instead, all custom objects must be referenced using their short-hand custom object type name, `fullyQualifiedName`, or `objectTypeId`. To avoid issues, update the following fields accordingly:
 >
 >- **Object Type** and **ObjectType to associate** in **Upsert Custom Object Record** action
 >- **Object Type** field in **Custom Event V2** action

Original file line number	Diff line number	Diff line change
`@@ -17,7 +17,7 @@ HubSpot is an all-in-one marketing tool that helps attract new leads and convert`
`17`	`17`	`When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your data to [HubSpot's REST API](https://developers.hubspot.com/docs/api/overview){:target="_blank"}.`
`18`	`18`
`19`	`19`	`> warning ""`
`20`		`-> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their base names. HubSpot mandates that custom objects should be referenced by short-hand custom object type name, fullyQualifiedName, or objectTypeId. To avoid issues, ensure the following fields are updated accordingly:`
	`20`	+> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their base names. Instead, all custom objects must be referenced using their short-hand custom object type name, `fullyQualifiedName`, or `objectTypeId`. To avoid issues, update the following fields accordingly:
`21`	`21`	`>`
`22`	`22`	`>- Object Type and ObjectType to associate in Upsert Custom Object Record action`
`23`	`23`	`>- Object Type field in Custom Event V2 action`