From 998865eba881a601787b712c67a56e9f7198955c Mon Sep 17 00:00:00 2001 From: Sarthak Choudhary Date: Tue, 15 Oct 2024 23:41:00 +0530 Subject: [PATCH] fix typo in bitfields page --- content/develop/data-types/bitfields.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/develop/data-types/bitfields.md b/content/develop/data-types/bitfields.md index 78718228a3..16482b3229 100644 --- a/content/develop/data-types/bitfields.md +++ b/content/develop/data-types/bitfields.md @@ -31,7 +31,7 @@ Bitfields support atomic read, write and increment operations, making them a goo ## Example -Suppose you want to maintain two metrics for various bicycles: the current price and the number of owners over time. You can represent these counters with a 32-bit wide bitfield per for each bike. +Suppose you want to maintain two metrics for various bicycles: the current price and the number of owners over time. You can represent these counters with a 32-bit wide bitfield for each bike. * Bike 1 initially costs 1,000 (counter in offset 0) and has never had an owner. After being sold, it's now considered used and the price instantly drops to reflect its new condition, and it now has an owner (offset 1). After quite some time, the bike becomes a classic. The original owner sells it for a profit, so the price goes up and the number of owners does as well.Finally, you can look at the bike's current price and number of owners.