kokoro: format README.md with Google style.

BUG=None
TEST=Read it.

Change-Id: I477a4d18255c8cc5ed2e4eb903d6651615473ad6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2902914
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Commit-Queue: Junichi Uekawa <uekawa@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>

ci/README.md

@@ -62,8 +62,8 @@ this do?
     executed directly, other tests require privileged access to devices and will
     be loaded into the VM to execute.
 
-   Each test will in the end be executed by a call to
-   `cargo test -p crate_name`.
+    Each test will in the end be executed by a call to `cargo test -p
+    crate_name`.
 
 Intermediate build data is stored in a scratch directory at `./target/ci/` to
 allow for faster subsequent calls (Note: If running with docker, these files
@@ -78,8 +78,8 @@ To only run x86 tests: `./ci/[aarch64_]builder --vm ./run_tests`.
 To run a simple test (e.g. the tempfile crate) that does not need the vm:
 `./ci/[aarch64_]builder cargo test -p tempfile`.
 
-Or run a single test (e.g. kvm_sys) inside the vm:
-`./ci/[aarch64*]builder --vm cargo test -p kvm_sys`.
+Or run a single test (e.g. kvm_sys) inside the vm: `./ci/[aarch64*]builder --vm
+cargo test -p kvm_sys`.
 
 Since the VM (especially the fully emulated aarch64 VM) can be slow to boot, you
 can start an interactive shell and run commands from there as usual. All cargo
@@ -115,8 +115,8 @@ Directories:
 -   ci/crosvm_builder: A native docker image for building and testing crosvm
 -   ci/crosvm_test_vm: Dockerfile to build the VM included in the builder
     containers.
-- ci/kokoro: Configuration files and build scripts used by Kokoro to run crosvm
-  tests.
+-   ci/kokoro: Configuration files and build scripts used by Kokoro to run
+    crosvm tests.
 
 Scripts: