@@ -262,8 +262,9 @@ after updating.
262
262
Contributing to the documentation
263
263
=================================
264
264
265
- If you're not the developer type, contributing to the documentation is still of
266
- huge value. You don't even have to be an expert on *pandas * to do so! In fact,
265
+ Contributing to the documentation benefits everyone who uses *pandas *.
266
+ We encourage you to help us improve the documentation, and
267
+ you don't have to be an expert on *pandas * to do so! In fact,
267
268
there are sections of the docs that are worse off after being written by
268
269
experts. If something in the docs doesn't make sense to you, updating the
269
270
relevant section after you figure it out is a great way to ensure it will help
@@ -292,12 +293,9 @@ Some other important things to know about the docs:
292
293
overviews per topic together with some other information (what's new,
293
294
installation, etc).
294
295
295
- - The docstrings follow the **Numpy Docstring Standard **, which is used widely
296
- in the Scientific Python community. This standard specifies the format of
297
- the different sections of the docstring. See `this document
298
- <https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt> `_
299
- for a detailed explanation, or look at some of the existing functions to
300
- extend it in a similar manner.
296
+ - The docstrings follow a pandas convention, based on the **Numpy Docstring
297
+ Standard **. Follow the :ref: `pandas docstring guide <docstring >` for detailed
298
+ instructions on how to write a correct docstring.
301
299
302
300
- The tutorials make heavy use of the `ipython directive
303
301
<http://matplotlib.org/sampledoc/ipython_directive.html> `_ sphinx extension.
0 commit comments