@@ -170,7 +170,7 @@ unsigned int32 i = (h_top_bits * z_as_64_bit) >> 32;
170170```
171171
172172The first line extracts the most significant 32 bits from ` h ` and
173- assignes them to a 64-bit unsigned integer. The second line is
173+ assigns them to a 64-bit unsigned integer. The second line is
174174simpler: it just sets an unsigned 64-bit value to the same value as
175175the 32-bit unsigned value ` z ` . The purpose of having both ` h_top_bits `
176176and ` z_as_64_bit ` be 64-bit values is so that their product is a
@@ -233,14 +233,14 @@ with a seed of 0 and [following the specification version
233233
234234The ` check ` operation in SBBFs can return ` true ` for an argument that
235235was never inserted into the SBBF. These are called "false
236- positives". The "false positive probabilty " is the probability that
236+ positives". The "false positive probability " is the probability that
237237any given hash value that was never ` insert ` ed into the SBBF will
238238cause ` check ` to return ` true ` (a false positive). There is not a
239239simple closed-form calculation of this probability, but here is an
240240example:
241241
242242A filter that uses 1024 blocks and has had 26,214 hash values
243- ` insert ` ed will have a false positive probabilty of around 1.26%. Each
243+ ` insert ` ed will have a false positive probability of around 1.26%. Each
244244of those 1024 blocks occupies 256 bits of space, so the total space
245245usage is 262,144. That means that the ratio of bits of space to hash
246246values is 10-to-1. Adding more hash values increases the denominator
0 commit comments