update references old variables style rules page

Author: RDaxini

docs/sphinx/source/contributing/style_guide.rst

@@ -13,7 +13,7 @@ pvlib python generally follows the `PEP 8 -- Style Guide for Python Code
 is 79 characters.
 
 pvlib python uses a mix of full and abbreviated variable names. See
-:ref:`variables_style_rules`. We could be better about consistency.
+:ref:`glossary`. We could be better about consistency.
 Prefer full names for new contributions. This is especially important
 for the API. Abbreviations can be used within a function to improve the
 readability of formulae.

docs/sphinx/source/index.rst

@@ -26,7 +26,7 @@ pvlib python
 that-use-pvlib-python>`_ page for inspiration and listing of your
 application.
 
-There is a :ref:`variable naming convention <variables_style_rules>` to
+There is a :ref:`variable naming convention <glossary>` to
 ensure consistency throughout the library.
 
 

docs/sphinx/source/user_guide/index.rst

@@ -15,7 +15,6 @@ User Guide
    clearsky
    bifacial
    weather_data
-   variables_style_rules
    glossary
    singlediode
    faq

docs/sphinx/source/user_guide/weather_data.rst

@@ -83,7 +83,7 @@ a :py:class:`pandas.DataFrame` of the actual dataset, plus a metadata
 dictionary.  Most :py:mod:`pvlib.iotools` functions also have
 a ``map_variables`` parameter to automatically translate
 the column names used in the data file (which vary widely from dataset to dataset)
-into standard pvlib names (see :ref:`variables_style_rules`).  
+into standard pvlib names (see :ref:`glossary`).  
 
 Typical usage looks something like this:
 

pvlib/iotools/midc.py

@@ -193,7 +193,7 @@ def read_midc(filename, variable_map={}, raw_data=False, **kwargs):
 
     See the MIDC_VARIABLE_MAP for collection of mappings by site.
     For a full list of pvlib variable names see the
-    :ref:`variables_style_rules`.
+    :ref:`glossary`.
 
     Be sure to check the units for the variables you will use on the
     `MIDC site <https://midcdmz.nrel.gov/>`_.