Helper script for doing release train related project branching and tagging.

[simantics/platform.git] / releng / doc / release.md

diff --git a/releng/doc/release.md b/releng/doc/release.md
index 3f4d69bfae3222248afa0446d6040239f09286f9..93796ce1436fb66a5691fd377f8187ba1f0d4f84 100644 (file)
--- a/releng/doc/release.md
+++ b/releng/doc/release.md
@@ -41,7 +41,7 @@ Plug-in components that are part of the release train:
 
 Products that are part of the release train:
 * Simantics Desktop
-* Simantics System Dynamics Tool \r
+* Simantics System Dynamics Tool
   * This is Simantics Desktop with Simantics System Dynamics Tool features installed
 
 For simplicity, each of these components are versioned accoring to platform versioning, i.e. for Platform SDK 1.26.0 there will be Simantics Desktop 1.26.0, Sysdyn 1.26.0, and so on.
@@ -106,8 +106,8 @@ In the following steps, it is recommended to ensure every `.target` file is up-t
    with
 
    ~~~
-   location "http://www.simantics.org/download/master/release/x.y.z[.w]/maven" {
-   location "http://www.simantics.org/download/master/release/x.y.z[.w]/manual" {
+   location "http://www.simantics.org/download/release/x.y.z[.w]/maven" {
+   location "http://www.simantics.org/download/release/x.y.z[.w]/manual" {
    include "http://www.simantics.org/download/release/x.y.z[.w]/org.simantics.sdk.build.targetdefinition.tpd"
    location "http://www.simantics.org/download/release/x.y.z[.w]/sdk" {
    ~~~
@@ -298,4 +298,4 @@ Insert some general thoughts on the release...
 
 # TODO
 
-* Incorporate tutorial code in the platform repository as a separate folder to allow platform builds to directly ensure that the tutorial code still builds OK
\ No newline at end of file
+* Incorporate tutorial code in the platform repository as a separate folder to allow platform builds to directly ensure that the tutorial code still builds OK