Fix style

docs/ExpectAPI.md

@@ -335,8 +335,8 @@ Moreover, this code tests that the returned reason includes 'octopus'`:
 ```js
 test('fetchData() rejects to be error', async () => {
   const drinkOctopus = new Promise(() => {
-    throw 'yuck, octopus flavor'
-  })
+      throw new DisgustingFlavorError('yuck, octopus flavor');
+  });
 
   await expect(drinkOctopus).rejects.toMatch('octopus');
 });

docs/TestingAsyncCode.md

@@ -60,7 +60,7 @@ test('the data is peanut butter', () => {
 
 Be sure to return the assertion—if you omit this `return` statement, your test will complete before `fetchData` completes.
 
-If you expect a promise to be rejected use the .rejects` matcher. It works analogically to the .resolves` matcher. If the promise is fulfilled, the test will automatically fail.
+If you expect a promise to be rejected use the `.rejects` matcher. It works analogically to the `.resolves` matcher. If the promise is fulfilled, the test will automatically fail.
 
 ```js
 test('the fetch fails with an error', () => {

examples/async/__tests__/user-test.js

@@ -8,7 +8,7 @@ import * as user from '../user';
 
 // The assertion for a promise must be returned.
 it('works with promises', () => {
-  return expect(user.getUserName(5)).resolves.toEqual('Paul'));
+  return expect(user.getUserName(5)).resolves.toEqual('Paul');
 });
 
 // async/await can also be used.