Fixed "Output" - Welcome To The Tech Palace (Fixes #2156)

[TristanAppDev]

Changed "Output" to "=>" - Welcome To The Tech Palace

Related to #2202

[github-actions]

Dear TristanAppDev

Thank you for contributing to the Go track on Exercism! 💙
You will see some automated feedback below 🤖. It would be great if you can make sure your PR covers those points. This will save your reviewer some time and your change can be merged quicker.

• 📜 The following files usually contain very similar content.

  • concepts/<concept>/about.md
  • concepts/<concept>/introduction.md
  • exercises/concept/<exercise>/.docs/introduction.md

  Please check whether the changes you made to one of these also need to be applied to the others.

• 🔗 If your PR fully fixes an issue, please include the text Fixes #issue_no in any line of the PR description. This will make the issue be automatically be closed when the PR is merged. If your PR is related to an existing issue but does not fix it completely, please link the issue anywhere in the description of the PR with #issue_no. You can read more about this in Github: Linking a pull request to an issue

• ✍️ If your PR is not related to an existing issue (and is not self-explaining like a typo fix), please make sure the description explains why the change you made is necessary.

• 🔤 If your PR fixes an easy to identify typo, if would be great if you could check for that typo in the whole repo. For example, if you found Unicdoe, use "replace all" in your editor (or command line magic) to fix it consistently.

Dear Reviewer/Maintainer

• 📏 Make sure you set the appropriate x:size label for the PR. (This also works after merging, in case you forgot about it.)

• 🔍 Don't be too nit-picky. If the PR is a clear improvement compared to the status quo, it should be approved as clear signal this is good to be merged even if the minor comments you might have are not addressed by the contributor. Further improvement ideas can be captured in issues (if important enough) and implemented via additional PRs.

• 🤔 After reviewing the diff in the "Files changed" section, take a moment to think about whether there are changes missing from the diff. Does something need to be adjusted in other places so the code or content stays consistent?

_{Automated comment created by PR Commenter 🤖.}

[TristanAppDev]

This one looks kind of strange to me with the "=>".

AddBorder("Welcome!", 10)
// =>
// **********
// Welcome!
// **********

[andrerfcsantos]

Thanks for fixing this in this exercise too.

The changes you made are correct. However, this exercise also has code examples in the introduction. The content in that introduction in turn is also present in the introduction.md and about.md of the strings concept.

If it is not much to ask, can you fix the code examples in those files too?

[TristanAppDev]

Sure, I'll have a look.

[andrerfcsantos]

@TristanAppDev Are you still interested in finishing this and #2197? Totally ok if you are no longer interested, just let us know and we can finish it for you :)

[TristanAppDev]

I'm still interested. Just have been too busy last weeks.
Sorry for letting you wait.

[andrerfcsantos]

@TristanAppDev No problem, thanks for letting us know.

Finish when you have the time and if you lose interest that's ok too, just let us know.

[andrerfcsantos]

There has been some interest from other contributors to fix this issue across the track. Since I had some free time and to make sure this PR is not superseded by another or having someone doing duplicate work, I took the time to finish it so we can merge it!

Thanks again for this contribution.