From 6852a953fd18f3201675779bc4aacfe8bd713205 Mon Sep 17 00:00:00 2001
From: Paul Philippov <themactep@gmail.com>
Date: Mon, 28 Feb 2022 02:06:39 -0500
Subject: [PATCH 1/2] Update integration-kernel.md

---
 en/integration-kernel.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/en/integration-kernel.md b/en/integration-kernel.md
index 573ed38..4f9338a 100644
--- a/en/integration-kernel.md
+++ b/en/integration-kernel.md
@@ -20,11 +20,11 @@ CONFIG_IP_PNP_DHCP=y
 CONFIG_ROOT_NFS=y
 ```
 
-## The patch names
+## Patch files
 
-```
-These patch files should be named <number>-<description>.patch.
-The patch files coming with Buildroot should not contain any package version reference in their filename.
-The field <number> in the patch file name refers to the apply order, and shall start at 1
-It is preferred to pad the number with zeros up to 4 digits, like git-format-patch does. E.g.: 0001-foobar-the-buz.patch
-```
\ No newline at end of file
+Patch files should be named `<number>-<description>.patch`.
+- The patch files should not contain any package version reference in their filename.
+- The field `<number>` in the patch file name refers to the apply order, and shall start at 1.
+It is preferred to pad the number with zeros up to 4 digits, like git-format-patch does. E.g.: _0001-foobar-the-buz.patch_
+- A message explaining what the patch does, and why it is needed, should be added in the header commentary of the patch.
+- You should add a Signed-off-by statement in the header of the each patch to help with keeping track of the changes and to certify that the patch is released under the same license as the software that is modified.

From d10e5a42f846310678f2b7b8e1c4f54f713b6ab7 Mon Sep 17 00:00:00 2001
From: Igor Zalatov <flyrouter@gmail.com>
Date: Tue, 1 Mar 2022 16:08:10 +0300
Subject: [PATCH 2/2] Fix typo

---
 en/menu-index.md | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/en/menu-index.md b/en/menu-index.md
index 9270158..58fd69f 100644
--- a/en/menu-index.md
+++ b/en/menu-index.md
@@ -107,16 +107,13 @@ You can help us to write a better documentation, proofread and correct our websi
 You can just donate some money to cover the cost of development and long-term maintaining of what we believe
 is going to be the most stable, flexible, and open IP Network Camera Framework for users like yourself.
 
-You can make a financial contribution to the project
-at [Open Collective](https://opencollective.com/openipc/contribute/backer-14335/checkout),
-or via [PayPal](https://www.paypal.com/donate/?hosted_button_id=C6F7UJLA58MBS),
-or via [YooMoney](https://openipc.org/donation/yoomoney.html).
+You can make a financial contribution to the project at [Open Collective](https://opencollective.com/openipc/contribute/backer-14335/checkout).
 
 Thank you.
 
+<p align="center">
 <a href="https://opencollective.com/openipc/contribute/backer-14335/checkout" target="_blank"><img src="https://opencollective.com/webpack/donate/button@2x.png?color=blue" width="375" alt="Open Collective donate button"></a>
-<a href="https://www.paypal.com/donate/?hosted_button_id=C6F7UJLA58MBS"><img src="https://www.paypalobjects.com/en_US/IT/i/btn/btn_donateCC_LG.gif" alt="PayPal donate button"></a>
-<a href="https://openipc.org/donation/yoomoney.html"><img src="https://yoomoney.ru/transfer/balance-informer/balance?id=596194605&key=291C29A811B500D7" width="140" alt="YooMoney donate button"></a>
+</p>
 
 
 [burn]: https://github.com/OpenIPC/burn