diff --git a/docs/sphinx/source/user_guide/faq.rst b/docs/sphinx/source/user_guide/faq.rst
index 15d7a04ac4..39e3bec841 100644
--- a/docs/sphinx/source/user_guide/faq.rst
+++ b/docs/sphinx/source/user_guide/faq.rst
@@ -66,7 +66,7 @@ irradiance datasets, including the BSRN, SURFRAD, SRML, and NREL's MIDC.
 Can I use PVsyst (PAN/OND) files with pvlib?
 --------------------------------------------
 
-Although pvlib does include a function to read PAN and OND files
+Although pvlib includes a function to read PAN and OND files
 (:py:func:`~pvlib.iotools.read_panond`), it is up to the user to determine
 whether and how the imported parameter values can be used with pvlib's models.
 Easier use of these parameter files with the rest of pvlib may be added
diff --git a/pvlib/iotools/panond.py b/pvlib/iotools/panond.py
index 81bea8ec05..7c524837fd 100644
--- a/pvlib/iotools/panond.py
+++ b/pvlib/iotools/panond.py
@@ -72,10 +72,10 @@ def parse_panond(fbuf):
     files was available. So, this parser is based on inferred logic, rather
     than anything specified by PVsyst.
 
-    The parser assumes that the file being parsed uses indendation of two
-    spaces ('  ') to create new level in a nested dictionary, and that
+    The parser assumes that the file being parsed uses indentation of two
+    spaces ('  ') to create a new level in a nested dictionary, and that
     key/values pairs of interest are separated using '='. This further means
-    that lines not containing '=' were omitted from the final returned
+    that lines not containing '=' are omitted from the final returned
     dictionary.
 
     Additionally, the indented lines often contain values themselves. This