"Send Personalized Texts Using Templates" --> "Personalize Text Messages With Templates"
"Templates can save time and effort when the same message format is required. Furthermore, your customers will receive personalized messages even when you’ve applied templates. All you have to do is use the embed tags into the template text." -->
"Message templates save time and effort when you need to customize a message for many recipients. All you need to do is embed template tags in your message text." NOTE: the second sentence (starting with Furthermore) sounds terrible, I recommend just omitting it. ALSO: this page calls tags "embed tags" and "merge tags", I'm recommending that you call them "template tags".
"Note, this command has no parameters." --> "Note, this command takes no parameters."
"The response you receive will have the format:" --> "You will receive a message with this format:"
"Template ID." --> "The template ID."
"Time when template was last modified." --> "The time when the template was last modified."
"Template name." --> "The template name."
"Template text. May contain the tags listed below." --> "The template text. See the template tags listed below.
"Custom fields list (Merge tags)" --> "Template tags"
"All tags should be inputted inside curly braces (e.g., {First name} for First name)." --> "All tags must be enclosed by curly braces e.g., {First name}."
"Contact first name." --> "The contact's first name."
"Contact last name." --> "The contact's last name."
"Contact last name." --> "The contact's last name."
"Contact company." --> "The contact's company."
"Contact phone number." --> "The contact's phone number."
"Email." --> "The contact's email address."
"Contact custom field values." --> "Custom field values for the contact."
NOTE: I like the word "recipient" better than Contact but I stayed with Contact because that is one of your API entity types.
"There are times when creating a new template makes sense (such as when targeting specific clients or improving your business strategies). You can create new SMS templates for marketing purposes or SMS templates for business campaigns." -->
"You can create new SMS templates for new marketing or business campaigns. "
"Template name." --> "The template name."
"Template text. May contain tags listed above." --> "The template text. See the template tags listed above."
"ID of the new template." --> "The ID of the new template."
"Link to the new template." --> "The URI to the new template." NOTE: I'd go with URI over URL here since this is a REST API.
"If successful, you will receive the standard link response:" --> "If successful, you will receive a response with these fields:"
"Note, this command has no parameters. If successful, this command will return the standard delete response (204 No Content), otherwise you will receive the standard error response." -->
"Note, this command takes no parameters. If successful, this command will return a standard delete response (204 No Content), otherwise you will receive a standard error response."
"Now you have learned how to create and manage SMS templates, please also check the Messages: Send section to learn how to send personalized text messages using these templates." --> "Now that you've learned how to create and manage SMS templates, please see the Messages: Send section to learn how to send personalized text messages using these templates."
"Send Personalized Texts Using Templates" --> "Personalize Text Messages With Templates"
"Templates can save time and effort when the same message format is required. Furthermore, your customers will receive personalized messages even when you’ve applied templates. All you have to do is use the embed tags into the template text." -->
"Message templates save time and effort when you need to customize a message for many recipients. All you need to do is embed template tags in your message text." NOTE: the second sentence (starting with Furthermore) sounds terrible, I recommend just omitting it. ALSO: this page calls tags "embed tags" and "merge tags", I'm recommending that you call them "template tags".
"Note, this command has no parameters." --> "Note, this command takes no parameters."
"The response you receive will have the format:" --> "You will receive a message with this format:"
"Template ID." --> "The template ID."
"Time when template was last modified." --> "The time when the template was last modified."
"Template name." --> "The template name."
"Template text. May contain the tags listed below." --> "The template text. See the template tags listed below.
"Custom fields list (Merge tags)" --> "Template tags"
"All tags should be inputted inside curly braces (e.g., {First name} for First name)." --> "All tags must be enclosed by curly braces e.g., {First name}."
"Contact first name." --> "The contact's first name."
"Contact last name." --> "The contact's last name."
"Contact last name." --> "The contact's last name."
"Contact company." --> "The contact's company."
"Contact phone number." --> "The contact's phone number."
"Email." --> "The contact's email address."
"Contact custom field values." --> "Custom field values for the contact."
NOTE: I like the word "recipient" better than Contact but I stayed with Contact because that is one of your API entity types.
"There are times when creating a new template makes sense (such as when targeting specific clients or improving your business strategies). You can create new SMS templates for marketing purposes or SMS templates for business campaigns." -->
"You can create new SMS templates for new marketing or business campaigns. "
"Template name." --> "The template name."
"Template text. May contain tags listed above." --> "The template text. See the template tags listed above."
"ID of the new template." --> "The ID of the new template."
"Link to the new template." --> "The URI to the new template." NOTE: I'd go with URI over URL here since this is a REST API.
"If successful, you will receive the standard link response:" --> "If successful, you will receive a response with these fields:"
"Note, this command has no parameters. If successful, this command will return the standard delete response (204 No Content), otherwise you will receive the standard error response." -->
"Note, this command takes no parameters. If successful, this command will return a standard delete response (204 No Content), otherwise you will receive a standard error response."
"Now you have learned how to create and manage SMS templates, please also check the Messages: Send section to learn how to send personalized text messages using these templates." --> "Now that you've learned how to create and manage SMS templates, please see the Messages: Send section to learn how to send personalized text messages using these templates."