clarify the changelog

MinnPost · Feb 23, 2018 · 652d124 · 652d124
1 parent a6a6c0d
commit 652d124
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/changelog.md b/changelog.md
@@ -3,7 +3,7 @@ Changelog
 
 * 1.2.7 (2018-02-23)
 	* Bug fix: in some cases, a fieldmap with the Salesforce update trigger checked, but not the Salesforce create trigger, it would still create data in WordPress. This data should, rather, be skipped.
-	* There are also a number of small tweaks to documentation and code comments.
+	* New: there are also a number of small tweaks to in-page help, documentation and code comments.
 
 * 1.2.6 (2018-01-30)
 	* Bug fix: in some cases, date fields coming from Salesforce were not correctly formatted for use in WordPress. This release causes any core date fields to be formatted as WordPress expects them. Thanks to GitHub user @prowp for the report on this.

diff --git a/readme.txt b/readme.txt
@@ -137,7 +137,7 @@ If you load Object Sync for Salesforce and then store data for a new meta field
 
 * 1.2.7 (2018-02-23)
 	* Bug fix: in some cases, a fieldmap with the Salesforce update trigger checked, but not the Salesforce create trigger, it would still create data in WordPress. This data should, rather, be skipped.
-	* There are also a number of small tweaks to documentation and code comments.
+	* New: there are also a number of small tweaks to in-page help, documentation and code comments.
 
 * 1.2.6 (2018-01-30)
 	* Bug fix: in some cases, date fields coming from Salesforce were not correctly formatted for use in WordPress. This release causes any core date fields to be formatted as WordPress expects them. Thanks to GitHub user @prowp for the report on this.