From 9b595dce51db4dc2cc0bc25ca976527d8a2c9bc7 Mon Sep 17 00:00:00 2001 From: GitHub Date: Thu, 21 Dec 2023 00:17:18 +0000 Subject: [PATCH] update documentation --- docs/lnd/code_contribution_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lnd/code_contribution_guidelines.md b/docs/lnd/code_contribution_guidelines.md index 79f03df6..90adc57c 100644 --- a/docs/lnd/code_contribution_guidelines.md +++ b/docs/lnd/code_contribution_guidelines.md @@ -331,7 +331,7 @@ Examples of common patterns w.r.t commit structures within the project: * Project or package wide file renamings should be in their own commit. * Ideally if a new package/struct/sub-system is added in a PR, there should be a single commit which adds the new functionality, with follow up - induvidual commits that begin to intergrate the functionality within the + individual commits that begin to integrate the functionality within the codebase. * If a PR only fixes a trivial issue, such as updating documentation on a small scale, fix typos, or any changes that do not modify the code, the