From 68934353f28a34b846e4cd93988e2e81f23dfd4d Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Wed, 16 Feb 2022 10:53:30 -0700 Subject: [PATCH] Typo fix (#23152) (#23153) Fixed a type in the documentation. (cherry picked from commit bb50259956168289804352fd1218ef7a3798abf7) Co-authored-by: Jerry --- docs/src/developing/on-chain-programs/developing-c.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/developing/on-chain-programs/developing-c.md b/docs/src/developing/on-chain-programs/developing-c.md index d82877c8ac..58ec1f0781 100644 --- a/docs/src/developing/on-chain-programs/developing-c.md +++ b/docs/src/developing/on-chain-programs/developing-c.md @@ -140,7 +140,7 @@ the [runtime enforcement policy](developing/programming-model/accounts.md#policy). When an instruction reference the same account multiple times there may be duplicate `SolAccountInfo` entries in the array but they both point back to the original -input byte array. A program should handle these case delicately to avoid +input byte array. A program should handle these cases delicately to avoid overlapping read/writes to the same buffer. If a program implements their own deserialization function care should be taken to handle duplicate accounts appropriately.