Improve messages and task descriptions for better consistency and clarity

docs/src/content/hardhat-runner/docs/getting-started/index.md

@@ -117,7 +117,7 @@ GLOBAL OPTIONS:
 
 AVAILABLE TASKS:
 
-  check                 Check whatever you need
+  check                 Runs a user-defined check
   clean                 Clears the cache and deletes all artifacts
   compile               Compiles the entire project, building all artifacts
   console               Opens a hardhat console
@@ -239,6 +239,24 @@ Compiled 2 Solidity files successfully
 
 ### Deploying your contracts
 
+In Hardhat v3, we use Hardhat Ignition for deploying contracts. Hardhat Ignition is a new declarative deployment system that offers several improvements:
+
+1. Declarative deployments
+2. Built-in error handling and recovery
+3. Improved testability
+4. Enhanced modularity
+
+To deploy the `Lock` contract, use the following command:
+
+```
+npx hardhat ignition deploy ./ignition/modules/Lock.js
+```
+
+
+This will deploy the Ignition module located in `./ignition/modules/Lock.js`.
+
+For more details on Hardhat Ignition and its features in Hardhat v3, refer to the [Hardhat Ignition documentation](/ignition).
+
 Next, to deploy the contract we will use a Hardhat Ignition module.
 
 Inside the `ignition/modules` folder you will find a file with the following code:

docs/src/content/hardhat-runner/docs/guides/deploying.md

@@ -1,8 +1,10 @@
 # Deploying your contracts
 
-To deploy your contracts, you can use [Hardhat Ignition](/ignition), our declarative deployment system. You can deploy the `Lock` contract from the sample project by using its accompanying Ignition module. An Ignition module is a TypeScript or JavaScript file that allows you to specify what needs to be deployed.
+To deploy your contracts, we recommend using [Hardhat Ignition](/ignition), our declarative deployment system. Hardhat Ignition is now the preferred method for deploying contracts in Hardhat v3.
 
-In the sample project, the Ignition module `LockModule` which deploys the `Lock` contract, is under the `./ignition/modules` directory and looks like this:
+In the sample project, you'll find an Ignition module for deploying the `Lock` contract. An Ignition module is a TypeScript or JavaScript file that specifies what needs to be deployed.
+
+The `LockModule` which deploys the `Lock` contract is located in the `./ignition/modules` directory and looks like this:
 
 ::::tabsgroup{options="TypeScript,JavaScript"}
 
@@ -60,4 +62,11 @@ If no network is specified, Hardhat Ignition will run against an in-memory insta
 
 In the sample `LockModule` above, two module parameters are used: `unlockTime` which will default to the 1st of Jan 2030 and `lockedAmount` which will default to one Gwei. You can learn more about overriding these values by providing your own module parameters during deployment in our [Deploying a module](/ignition/docs/guides/deploy#defining-parameters-during-deployment) guide.
 
+Hardhat Ignition, introduced in Hardhat v3, brings several improvements to the deployment process:
+
+1. Declarative deployments: Define your entire deployment pipeline in a single, easy-to-understand module.
+2. Built-in error handling and recovery: Automatically resume deployments from where they left off if interrupted.
+3. Improved testability: Easily integrate deployments into your test suite.
+4. Enhanced modularity: Create reusable deployment modules for different parts of your project.
+
 Read more about Hardhat Ignition generally in the [Hardhat Ignition documentation](/ignition).

docs/src/content/hardhat-runner/docs/guides/tasks.md

@@ -25,6 +25,14 @@ Now you should be able to run it:
 ```
 npx hardhat accounts
 ```
+For tasks that support network parameters, you can specify the network like this:
+
+
+```
+npx hardhat compile --network localhost
+```
+This will run the task on the specified network (in this case, localhost).
+
 
 We are using the `task` function to define our new task. Its first argument is the name of the task, and it's what we use in the command line to run it. The second argument is the description of the task, which is printed when you use `npx hardhat help`.
 

packages/hardhat-core/src/builtin-tasks/check.ts

@@ -2,4 +2,4 @@ import { task } from "../internal/core/config/config-env";
 
 import { TASK_CHECK } from "./task-names";
 
-task(TASK_CHECK, "Check whatever you need", async () => {});
+task(TASK_CHECK, "Runs a user-defined check", async () => {});

packages/hardhat-core/src/internal/cli/cli.ts

@@ -170,14 +170,10 @@ async function main() {
 
         // Warning for Hardhat V3 deprecation
         console.warn(
-          chalk.yellow.bold("\n\nDEPRECATION WARNING\n\n"),
+          chalk.yellow.bold("DEPRECATION WARNING: "),
           chalk.yellow(
-            `Initializing a project with ${chalk.white.italic(
-              "npx hardhat"
-            )} is deprecated and will be removed in the future.\n`
-          ),
-          chalk.yellow(
-            `Please use ${chalk.white.italic("npx hardhat init")} instead.\n\n`
+            `Using ${chalk.white.italic("npx hardhat")} to initialize a project is deprecated.\n`,
+            `Please use ${chalk.white.italic("npx hardhat init")} instead.\n`
           )
         );