From 4c232f451439705538226776e5e28dee6b899c26 Mon Sep 17 00:00:00 2001 From: Cyphadoc Date: Wed, 28 Aug 2024 17:33:29 +0100 Subject: [PATCH] Update explore-the-code.md (#2096) Changed the preposition of 'specify' from 'is' to 'as' for better clarity. Co-authored-by: Shawn Tabrizi --- content/md/en/docs/quick-start/explore-the-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/md/en/docs/quick-start/explore-the-code.md b/content/md/en/docs/quick-start/explore-the-code.md index be6fb4f9e..11a25a3fa 100644 --- a/content/md/en/docs/quick-start/explore-the-code.md +++ b/content/md/en/docs/quick-start/explore-the-code.md @@ -48,7 +48,7 @@ From this manifest, you see that the node template workspace includes three pack - The `runtime` package provides all of the application logic for handling accounts, balances, transaction fees, and other features that have been included in the node template. Each member package also has its own manifest—its own `Cargo.toml` file—that contains package-specific information, including dependencies and configuration settings, that are required to compile that member package. -For example, the `Cargo.toml` file for the `node` member of the workspace specifies the name of the package is `node-template` and lists the core libraries and primitives that enable the node template to provide essential blockchain services. +For example, the `Cargo.toml` file for the `node` member of the workspace specifies the name of the package as `node-template` and lists the core libraries and primitives that enable the node template to provide essential blockchain services. You'll learn more about libraries and primitives in [Architecture and Rust libraries](/learn/architecture). For now, it's enough to understand the importance of the manifest in describing dependencies and other critical information for each package.