Updating README.md (#258)

README.md

@@ -73,7 +73,7 @@ The `npm start` command first compiles the application,
 then simultaneously re-compiles and runs the `lite-server`.
 Both the compiler and the server watch for file changes.
 
-Shut it down manually with Ctrl-C.
+Shut it down manually with `Ctrl-C`.
 
 You're ready to write your application.
 
@@ -114,11 +114,11 @@ Run it with `npm test`
 That command first compiles the application, then simultaneously re-compiles and runs the karma test-runner.
 Both the compiler and the karma watch for (different) file changes.
 
-Shut it down manually with Ctrl-C.
+Shut it down manually with `Ctrl-C`.
 
 Test-runner output appears in the terminal window.
 We can update our app and our tests in real-time, keeping a weather eye on the console for broken tests.
-Karma is occasionally confused and it is often necessary to shut down its browser or even shut the command down (Ctrl-C) and
+Karma is occasionally confused and it is often necessary to shut down its browser or even shut the command down (`Ctrl-C`) and
 restart it. No worries; it's pretty quick.
 
 ### End-to-end (E2E) Tests
@@ -139,7 +139,7 @@ The pass/fail test results appear at the bottom of the terminal window.
 A custom reporter (see `protractor.config.js`) generates a  `./_test-output/protractor-results.txt` file
 which is easier to read; this file is excluded from source control.
 
-Shut it down manually with Ctrl-C.
+Shut it down manually with `Ctrl-C`.
 
 [travis-badge]: https://travis-ci.org/angular/quickstart.svg?branch=master
 [travis-badge-url]: https://travis-ci.org/angular/quickstart