aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJuergen Haug2018-07-06 11:21:26 -0400
committerJuergen Haug2018-07-06 11:21:26 -0400
commita276257dc95ffd20597aea3daddd01016eaed008 (patch)
tree0954c7e9aeaf1bb7db7c4684b5f42b09c0fb4646
parentefc0339ae13833e5b3bc281b9707979be938f870 (diff)
downloadorg.eclipse.etrice-a276257dc95ffd20597aea3daddd01016eaed008.tar.gz
org.eclipse.etrice-a276257dc95ffd20597aea3daddd01016eaed008.tar.xz
org.eclipse.etrice-a276257dc95ffd20597aea3daddd01016eaed008.zip
[doc] minor improvement
-rw-r--r--plugins/org.eclipse.etrice.doc/online-doc/content/release-notes.md2
-rw-r--r--plugins/org.eclipse.etrice.doc/targets/eclipse-help/release-notes.html2
2 files changed, 2 insertions, 2 deletions
diff --git a/plugins/org.eclipse.etrice.doc/online-doc/content/release-notes.md b/plugins/org.eclipse.etrice.doc/online-doc/content/release-notes.md
index 9f8f7f323..7329afb66 100644
--- a/plugins/org.eclipse.etrice.doc/online-doc/content/release-notes.md
+++ b/plugins/org.eclipse.etrice.doc/online-doc/content/release-notes.md
@@ -21,6 +21,6 @@ eTrice provides a **migration action** which automatically applies the modificat
<span class="label label-info">Note:</span> The migration assistant relies on the message data names, thus the names should not be removed until you have fully migrated your project and all dependent projects.
<br/>
-In addition eTrice now uses the so-called *Smart Strings* for user code. This is not a breaking change, but it is recommended to migrate to this new syntax also. Using the Transition Data migration action will automatically convert all affected user codes into Smart Strings. Further there is a dedicated migration action for the Smart Strings, see **Migrate to Smart Action Codes** above. Additionally there is a quickfix available:
+In addition eTrice now uses the so-called **Smart Strings** for user code. This is not a breaking change, but it is recommended to migrate to this new syntax also. Using the Transition Data migration action will automatically convert all affected user codes into Smart Strings. Further there is a dedicated migration action for the Smart Strings, see *Migrate to Smart Action Codes* above. Additionally there is a quickfix available:
![image](images/600-DetailcodeMigration.png)
diff --git a/plugins/org.eclipse.etrice.doc/targets/eclipse-help/release-notes.html b/plugins/org.eclipse.etrice.doc/targets/eclipse-help/release-notes.html
index 8ebd5d2f7..de7f03d58 100644
--- a/plugins/org.eclipse.etrice.doc/targets/eclipse-help/release-notes.html
+++ b/plugins/org.eclipse.etrice.doc/targets/eclipse-help/release-notes.html
@@ -24,7 +24,7 @@
<p><img src="images/600-TransitionDataMigrationAssitant.png" alt="image"></p>
<p><span class="label label-info">Note:</span> The migration assistant relies on the message data names, thus the names should not be removed until you have fully migrated your project and all dependent projects.</p>
<br>
-<p>In addition eTrice now uses the so-called <em>Smart Strings</em> for user code. This is not a breaking change, but it is recommended to migrate to this new syntax also. Using the Transition Data migration action will automatically convert all affected user codes into Smart Strings. Further there is a dedicated migration action for the Smart Strings, see <strong>Migrate to Smart Action Codes</strong> above. Additionally there is a quickfix available:</p>
+<p>In addition eTrice now uses the so-called <strong>Smart Strings</strong> for user code. This is not a breaking change, but it is recommended to migrate to this new syntax also. Using the Transition Data migration action will automatically convert all affected user codes into Smart Strings. Further there is a dedicated migration action for the Smart Strings, see <em>Migrate to Smart Action Codes</em> above. Additionally there is a quickfix available:</p>
<p><img src="images/600-DetailcodeMigration.png" alt="image"></p>
</body>