DOC: Validating that the word pandas is correctly capitalized
- [x] closes #32316 
- [x] tests added / passed
- [x] passes `black pandas`
- [x] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [x] whatsnew entry

As suggested by @datapythonista , I've added checks in `ci/code_checks.sh` to look if the `pandas` is being referenced in a standardized way i.e `pandas`,  not ` *pandas* `  or  `Pandas`

@datapythonista I've only added checks to see if pandas is being referenced correctly, but not showing where it's changed or how many references are wrong. 
Should I add checks for that also ? What do you think ?
Can you have a look at the diff? I think something went wrong, there are lots of unrelated changes.  @datapythonista you're right, let me check what went wrong. @joybhallaa Can you run the following and push?

```
git checkout add-check-standard-pandas
git fetch upstream
git merge upstream/master
git reset --soft upstream/master
git commit -m "Fixed wrong diff"
```

---

Taken all of the commands above from https://datapythonista.me/blog/useful-git-commands.html @MomIsBestFriend okay, I'll do that ! > ```
> git checkout add-check-standard-pandas
> git fetch upstream
> git merge upstream/master
> git reset --soft upstream/master
> git commit -m "Fixed wrong diff"
> ```

@MomIsBestFriend I executed all these commands, and when pushing using `git push origin add-check-standard-pandas`, I got the error `hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.`

Let me check what's causing the problem and I'll push ASAP @joybhallaa Have you followed the steps in the [Contributing guide](https://dev.pandas.io/docs/development/contributing.html#id9)? @joybhallaa first try `git diff upstream/master` and see if now you've got the changes you're proposing in this PR. If that's the case, you need a `git push --force`, since you're rewriting the history here (replacing all these unwanted commits by the new single commit you just did). > @joybhallaa first try `git diff upstream/master` and see if now you've got the changes you're proposing in this PR. If that's the case, you need a `git push --force`, since you're rewriting the history here (replacing all these unwanted commits by the new single commit you just did).

@datapythonista done @joybhallaa do you have time to have a look at the previous comments? @datapythonista yep was busy with college stuff. Will start work ASAP > CI is green, and I don't think we fixed all the cases of `Pandas` and `*pandas*` in the docs and web, did we? If we didn't, this is not working.
> 
> We use `invgrep -R` everywhere else, I think we should use the same, may be that's the problem.
> 
> Also, can you add `PANDAS` please?

Sure Something is wrong here, @joybhallaa can you have a look at the diff, and leave things so this is ready for review please? @datapythonista yes.Working on it right now

EDIT: There is still one file with conflict.  @datapythonista should I open a new PR with a new branch ? This branch keeps giving me problems.  @joybhallaa I suggest you read https://datapythonista.me/blog/useful-git-commands.html

> I've got some cool changes, but my history is a mess @datapythonista the 2nd last commit only has the changes that I've made. 
Let me know if that's suitable > @datapythonista the 2nd last commit only has the changes that I've made.
> Let me know if that's suitable

No, we need a proper PR to be able to fix. @MomIsBestFriend gave you a resource to fix this. But probably better to open a new PR, closing this one, since your changes are small, and looks like it'll be easier to start again, than to fix this.