Meta tweaks

.github/security.md

@@ -0,0 +1,3 @@
+# Security Policy
+
+To report a security vulnerability, please use the [Tidelift security contact](https://tidelift.com/security). Tidelift will coordinate the fix and disclosure.

.github/workflows/main.yml

@@ -13,7 +13,6 @@ jobs:
  - 14
  - 12
  - 10
- - 8
  steps:
  - uses: actions/checkout@v2
  - uses: actions/setup-node@v1

license

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) Sindre Sorhus <[email protected]> (sindresorhus.com)
+Copyright (c) Sindre Sorhus <[email protected]> (https://sindresorhus.com)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 

package.json

@@ -4,10 +4,11 @@
  "description": "Run grunt tasks concurrently",
  "license": "MIT",
  "repository": "sindresorhus/grunt-concurrent",
+ "funding": "https:/sponsors/sindresorhus",
  "author": {
  "name": "Sindre Sorhus",
  "email": "[email protected]",
- "url": "sindresorhus.com"
+ "url": "https://sindresorhus.com"
  },
  "engines": {
  "node": ">=8"

readme.md

@@ -6,13 +6,11 @@
 
 Running slow tasks like Coffee and Sass concurrently can potentially improve your build time significantly. This task is also useful if you need to run [multiple blocking tasks](#logconcurrentoutput) like `nodemon` and `watch` at once.
 
-
 ## Install
 
+```sh
+npm install --save-dev grunt-concurrent
 ```
-$ npm install --save-dev grunt-concurrent
-```
-
 
 ## Usage
 
@@ -47,14 +45,14 @@ Now `jshint` will always be done before `coffee` and `sass` runs independent of
 
 ### limit
 
-Type: `number`<br>
+Type: `number`\
 Default: Twice the number of CPU cores with a minimum of 2
 
 Limit how many tasks that are run concurrently.
 
 ### logConcurrentOutput
 
-Type: `boolean`<br>
+Type: `boolean`\
 Default: `false`
 
 You can optionally log the output of your concurrent tasks by specifying the `logConcurrentOutput` option. Here is an example config which runs [grunt-nodemon](https:/ChrisWren/grunt-nodemon) to launch and monitor a node server and [grunt-contrib-watch](https:/gruntjs/grunt-contrib-watch) to watch for asset changes all in one terminal tab:
@@ -79,7 +77,7 @@ grunt.registerTask('default', ['concurrent:target']);
 
 ### indent
 
-Type: `boolean`<br>
+Type: `boolean`\
 Default: `true`
 
 You can optionally skip indenting the log output of your concurrent tasks by specifying `false`. This can be useful for running tasks in parallel for a stdout parser which expects no indentation, for example, TeamCity tests.