doc/develop/sending_patches.rst: Reword where our git tree is slightly

We shouldn't have had the link to our git tree be contained within "``"
as that meant that it did not work as a link, so remove those. And
rather than make this a link plus text, keep this as a link within the
text for overall clarity.

Suggested-by: Quentin Schulz <quentin.schulz@cherry.de>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Tom Rini <trini@konsulko.com>

diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index 9308f428bbdb2e762457666cb7380fd87220feee..e22b5e3e244eac9f7e451781a380caba93f2ab17 100644 (file)
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -76,11 +76,10 @@ General Patch Submission Rules
   compression, no attachments. Just plain text. The best way to generate
   patches is by using the ``git format-patch`` command. For a patch that is
   fixing a bug or regression of some sort, please use the ``master`` branch of
-  the mainline U-Boot git repository
-  (``https://source.denx.de/u-boot/u-boot.git``) as reference. For new
-  features, if the ``next`` branch has been opened (which happens with the
-  release of ``-rc2``) that branch should be used, otherwise ``master`` is
-  acceptable.
+  the mainline U-Boot git repository located at
+  https://source.denx.de/u-boot/u-boot.git as reference. For new features, if
+  the ``next`` branch has been opened (which happens with the release of
+  ``-rc2``) that branch should be used, otherwise ``master`` is acceptable.
 
 * Make sure that your mailer does not mangle the patch by automatic changes
   like wrapping of longer lines etc.