Skip to content

Commit 5ade549

Browse files
authored
Merge pull request #11 from flowerhack/master
Minor clarity/wording changes to README
2 parents 1e72dbf + 5ac5b54 commit 5ade549

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,9 +83,9 @@ Using the module
8383
----------------
8484

8585
As mentioned above, bitarray objects behave very much like lists, so
86-
there is not too new to learn. The biggest difference to list objects
86+
there is not too much to learn. The biggest difference from list objects
8787
is the ability to access the machine representation of the object.
88-
When doing so, the bit endianness is of importance, this issue is
88+
When doing so, the bit endianness is of importance; this issue is
8989
explained in detail in the section below. Here, we demonstrate the
9090
basic usage of bitarray objects:
9191

@@ -236,11 +236,11 @@ endianness:
236236
>>> a.tobytes() == b.tobytes()
237237
True
238238

239-
The default bit endianness is currently big-endian, however this may change
239+
The default bit endianness is currently big-endian; however, this may change
240240
in the future, and when dealing with the machine representation of bitarray
241241
objects, it is recommended to always explicitly specify the endianness.
242242

243-
Unless, explicitly converting to machine representation, using
243+
Unless explicitly converting to machine representation, using
244244
the ``tobytes``, ``frombytes``, ``tofile`` and ``fromfile`` methods,
245245
the bit endianness will have no effect on any computation, and one
246246
can safely ignore setting the endianness, and other details of this section.

0 commit comments

Comments
 (0)