I hate seeing typos as well. I contact TR support via their online contact form and report them.
What I do is open up the workout editor and find the typo. I take a screengrab and send this through to support. This makes it a lot easier for them as they can see the typo plus see the time it appears on screen. This makes it a lot easier to fix. Attached is what I mean.
Found one today in Taylor-2. In the first set of 14 intervals the text says something like ākeep going only 3 leftā but at that point there are actually 5 or 6 left. Later on in the same set the text re-appears correctly saying there are only 3 intervals left.
Who knew there is a workout editor. Great tip, there are so many times I am momentarily not paying attention and wish i could go back and see what was just put on the screen.
Spencer +2, with 4 intervals to go the text said 3 to go. Now I was pretty knackered, but I did spend a good 30 seconds counting to 4 at 120%. Funny what parts of your brain are deprioritized when you are trying not to die.
Did the Mount Field workout today. The workout is labeled as āTempoā but the text description talks about Sweet Spot work. In the analysis, the interval labels/titles on the 3 intervals are labeled as Sweet Spot 1, 2, and 3, but the power zones are all in the Tempo zone, not the Sweet Spot zone.
@Bikr, thanks so much for starting this thread! This is suuuuuper helpful to us.
Weāre always quick to fix typos when theyāre sent into Support, or we find them, but this is a great way for us to take care of many very quickly.
Iām going to have someone from my team drill in and correct each typo thatās been brought up here, and Iāll make sure we stay on top of new posts that trickle in over time.
Many, many thanks to everyone thatās posted! Youāre all helping make TR better.
I donāt actually mind the typos that much BUT āa couple minutesā is my pet hate, if you want to shorten āa couple OF minutesā then just write ātwo minutesā, āa couple minutesā just sounds all kinds of wrong to me.
Somewhat related: Martin Hill description on iOS shows āā¦than you?re likely to seeā¦ā So display encoding is different from the encoding for the text?