hc
2024-10-12 a5969cabbb4660eab42b6ef0412cbbd1200cf14d
kernel/Documentation/core-api/assoc_array.rst
....@@ -34,7 +34,7 @@
3434 8. The array can iterated over. The objects will not necessarily come out in
3535 key order.
3636
37
-9. The array can be iterated over whilst it is being modified, provided the
37
+9. The array can be iterated over while it is being modified, provided the
3838 RCU readlock is being held by the iterator. Note, however, under these
3939 circumstances, some objects may be seen more than once. If this is a
4040 problem, the iterator should lock against modification. Objects will not
....@@ -42,7 +42,7 @@
4242
4343 10. Objects in the array can be looked up by means of their index key.
4444
45
-11. Objects can be looked up whilst the array is being modified, provided the
45
+11. Objects can be looked up while the array is being modified, provided the
4646 RCU readlock is being held by the thread doing the look up.
4747
4848 The implementation uses a tree of 16-pointer nodes internally that are indexed
....@@ -273,7 +273,7 @@
273273 enough memory.
274274
275275 It is possible for other threads to iterate over or search the array under
276
-the RCU read lock whilst this function is in progress. The caller should
276
+the RCU read lock while this function is in progress. The caller should
277277 lock exclusively against other modifiers of the array.
278278
279279