Remove markdown formatting.

Author: HonkingGoose

TRANSLATING.md

@@ -70,9 +70,9 @@ On https://git-scm.com, the translations are divided into three categories. Once
 
 ## Continuous integration with Travis CI
 
-*Travis CI* is a [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) service that integrates with GitHub. *Travis CI* is used to ensure that a pull-request doesn't break the build or compilation. *Travis CI* can also provide compiled versions of the book.
+Travis CI is a [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) service that integrates with GitHub. Travis CI is used to ensure that a pull-request doesn't break the build or compilation. Travis CI can also provide compiled versions of the book.
 
-Setting up *Travis CI* requires administrative control over the repository.
+Setting up Travis CI requires administrative control over the repository.
 
 ### Registering for Travis continuous integration
 
@@ -82,7 +82,7 @@ Please refer to the [Travis documentation](https://docs.travis-ci.com/) for more
 
 ### Setting up your repository for continuous integration
 
-*Travis CI* works by scanning your project's root directory for a file named `.travis.yml` and following the 'recipe' that it contains. The good news is: there's already a working `.travis.yml` file in the Pro Git 2 source [here](https://raw.githubusercontent.com/progit/progit2-pub/master/travis.yml).
+Travis CI works by scanning your project's root directory for a file named `.travis.yml` and following the 'recipe' that it contains. The good news is: there's already a working `.travis.yml` file in the Pro Git 2 source [here](https://raw.githubusercontent.com/progit/progit2-pub/master/travis.yml).
 Copy that file, and put it in your working directory. Commit the .yml file and push it to your translation repository; that should fire up a compilation and a check of the book's contents.
 
 ## Setting up a publication chain for e-books