DOC: Fix GL01 and GL02 errors in the docstrings
- [x] closes #27986
- [ ] tests added / passed
- [x] passes `black pandas`
- [x] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

Fixed docstrings text that aren’t on the next line after opening `"""` and followed immediately by the line with closing `"""`. Issue #27986
Hello @steveayers124! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:





There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2019-08-24 05:57:03 UTC I appreciate your review, and encouragement, @datapythonista. I'll try going in smaller increments to see maybe what's failing, when I try more pull requests on my remaining changes. Thanks for the feedback! Agree on both @WillAyd. But I'm also happy to have them in a follow up. GL01 and GL02 are about the position of the quotes, and for formatting errors I'd say it may speed up things if we merge PRs fast and keep opening new tickets fast, than trying to address too many in the PRs.

I'm writing a blog post about what I think it makes sense, so we can discuss and find the way that we all find more efficient. But there is so much to say that it's taking forever. :) Sure - merge away

Sent from my iPhone

> On Aug 24, 2019, at 9:22 AM, Marc Garcia <notifications@github.com> wrote:
> 
> Agree on both @WillAyd. But I'm also happy to have them in a follow up. GL01 and GL02 are about the position of the quotes, and for formatting errors I'd say it may speed up things if we merge PRs fast and keep opening new tickets fast, than trying to address too many in the PRs.
> 
> I'm writing a blog post about what I think it makes sense, so we can discuss and find the way that we all find more efficient. But there is so much to say that it's taking forever. :)
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
 Thanks @steveayers124, keep the good work.