[rtems-docs commit] eng: Unicode char (U+200B)

[Sebastian Huber]

Module:    rtems-docs
Branch:    master
Commit:    e24c5e9682ee4d85474cbd326d25e99f0207731c
Changeset: http://git.rtems.org/rtems-docs/commit/?id=e24c5e9682ee4d85474cbd326d25e99f0207731c

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Thu Dec 20 08:19:05 2018 +0100

eng: Unicode char (U+200B)

---

 eng/vc-users.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eng/vc-users.rst b/eng/vc-users.rst
index efa29e0..d7ae90e 100644
--- a/eng/vc-users.rst
+++ b/eng/vc-users.rst
@@ -53,7 +53,7 @@ the command:
 
 This will create a local branch named "rtems410", containing the rtems-4.10
 release, that will track the remote branch "rtems-4-10-branch" in origin
-(​git://git.rtems.org/rtems.git). The ``git branch`` command prints a list of
+(git://git.rtems.org/rtems.git). The ``git branch`` command prints a list of
 the current local branches, indicating the one currently checked out.
 
 If you want to switch between local branches:
@@ -284,7 +284,7 @@ git reset
 
 ``git reset`` is a powerful and tricky command that should only be used on
 local (un-pushed) branches): A good description of what it enables to do can be
-found ​here. The following are a few useful examples. Note that adding a ~
+found here. The following are a few useful examples. Note that adding a ~
 after HEAD refers to the most recent commit, and you can add a number after
 the ~ to refer to commits even further back; HEAD by itself refers to the
 current working directory (changes since the last commit).
@@ -545,7 +545,7 @@ Troubleshooting
 ---------------
 
 Some restrictive corporate firewalls block access through the Git protocol
-(​git://). If you are unable to reach the server ​git://git.rtems.org/ you can
+(git://). If you are unable to reach the server git://git.rtems.org/ you can
 try accessing through http. To clone the rtems repository using the http
 protocol use the following command: