http2: Update documentation

- Calling abort no longer behaves like .destroy()
- Fix linting errors

doc/api/http2.md

@@ -887,9 +887,9 @@ close when the final `DATA` frame is transmitted. User code must call either
 `http2stream.sendTrailers()` or `http2stream.close()` to close the
 `Http2Stream`.
 
-When `options.signal` is set with an `AbortSignal` and then calling `abort` on
-the corresponding `AbortController` will behave the same way as calling
-`.destroy()` on the request itself.
+When `options.signal` is set with an `AbortSignal` and then `abort` on the
+corresponding `AbortController` is called, the request will emit an `'error'`
+event with an `AbortError` error.
 
 The `:method` and `:path` pseudo-headers are not specified within `headers`,
 they respectively default to:

test/parallel/test-http2-client-destroy.js

@@ -178,23 +178,23 @@ const Countdown = require('../common/countdown');
   server.listen(0, common.mustCall(() => {
     const client = h2.connect(`http://localhost:${server.address().port}`);
     client.on('close', common.mustCall());
-    
+
     const { signal } = controller;
     assert.strictEqual(signal[kEvents].get('abort'), undefined);
 
     client.on('error', common.mustCall(() => {
-      // After underlying stream dies, signal listener detached 
+      // After underlying stream dies, signal listener detached
       assert.strictEqual(signal[kEvents].get('abort'), undefined);
     }));
-    
+
     const req = client.request({}, { signal });
 
     req.on('error', common.mustCall((err) => {
       assert.strictEqual(err.code, 'ABORT_ERR');
       assert.strictEqual(err.name, 'AbortError');
     }));
     req.on('close', common.mustCall(() => server.close()));
-    
+
     assert.strictEqual(req.aborted, false);
     assert.strictEqual(req.destroyed, false);
     // Signal listener attached