Fixed typos

README.md

@@ -33,7 +33,7 @@ for f in het_obj.get_files():
         print(f)
 ```
 
-Print JSON metatdata::
+Print JSON metadata::
 
 ```python
 print(xmi_obj.get_json())

docs/cookbook.rst

@@ -20,7 +20,7 @@ To list all datasets and dataset members::
         else:
             print(f)
 
-Print JSON metatdata::
+Print JSON metadata::
 
     print(xmi_obj.get_json())
     print(het_obj.get_json(text=True)) # Adds plaintext files to json output

docs/iebcopy.rst

@@ -6,7 +6,7 @@ library we will talk about how it produces PDS unloads and their various
 controls records as well as the directory structure.
 
 ``IEBCOPY`` is used to *unload* partitioned datasets to a tape,
-vitual tape, xmi, file etc. Its format is made up of controls records (COPYR1
+virtual tape, xmi, file etc. Its format is made up of controls records (COPYR1
 and COPYR2), a listing of members and their metadata followed by the PDS
 members file data.
 
@@ -41,7 +41,7 @@ Directory Information
 ~~~~~~~~~~~~~~~~~~~~~
 
 Following the control records is the directory information. This section is
-vairable length and can span multiple blocks. It contains the member names
+variable length and can span multiple blocks. It contains the member names
 and metadata about the member. This section begins with::
 
     00 00 00 00 00 00 00 00

docs/netdata.rst

@@ -8,15 +8,15 @@ NETDATA files are primarily used to transfer sequential and partitioned
 datasets between mainframe environments, sometimes via non mainframe
 environments. NETDATA is the official name for the file format of the
 output from the z/OS ``TRANSMIT``, z/VM ``NETDATA`` or the opensource
-tool ``XMIT370``. However, it is more often reffered to as an ``XMI`` file.
-This documentation uses XMI and NETDATA interchangably. Typically third
+tool ``XMIT370``. However, it is more often referred to as an ``XMI`` file.
+This documentation uses XMI and NETDATA interchangeably. Typically third
 parties and even IBM will refer to them as XMI files.
 
 .. note::
     Some quick terminology:
 
-    - **Dataset**: a mainframe file, usually refered to as a sequential dataset or seq
-    - **Partitioned dataset**: a mainframe folder usually refered to as a PDS
+    - **Dataset**: a mainframe file, usually referred to as a sequential dataset or seq
+    - **Partitioned dataset**: a mainframe folder usually referred to as a PDS
     - **Member**: files in a partitioned dataset
     - **Unload**: extracting data to be used elsewhere
     - **LRECL**: The record length. This is how long each line in a file is,
@@ -38,7 +38,7 @@ parties and even IBM will refer to them as XMI files.
 
 
 XMI files contain either a sequential dataset or a partitioned dataset, and
-optionally a message. They cannot contain more than one dataset, paritioned
+optionally a message. They cannot contain more than one dataset, partitioned
 or sequential at a time. They can, however, also include an optional message
 which is technically sequential dataset, however the dataset name is lost.
 
@@ -220,7 +220,7 @@ Defines the file format and contains the following text units:
 INRM04 Records
 ~~~~~~~~~~~~~~
 
-INMR04 records are used to pass data to instalation specific exits
+INMR04 records are used to pass data to installation specific exits
 (i.e. APIs).
 
 

docs/virtualtape.rst

@@ -39,7 +39,7 @@ Each label/dataset stored on a virtual tape is preceded by a header record
         - 0x01 ZLIB compression
 
 Following the header record is data. On some tapes (not all) optional
-label records can exist. These records identify metatdata about the dataset(s)
+label records can exist. These records identify metadata about the dataset(s)
 on the tape. Each label starts with 3 characters and a number and are 80 bytes
 long. In HET files labels are compressed based on the flag.