Fix docs/development.md describing inaccurate issues

[sourcelliu]

What this PR does / why we need it:
In the file of docs/development.md. The following command cannot be executed.

$ TAG=<tag> REGISTRY=$USER/ingress-controller make docker-build
$ TAG=<tag> REGISTRY=$USER/ingress-controller make docker-push

The result of the execution is：

make: *** No rule to make target `docker-build'.  Stop.
make: *** No rule to make target `docker-push'.  Stop.

I checked the file of Makefile，I thought it shoud be:

$ TAG=<tag> REGISTRY=$USER/ingress-controller make container
$ TAG=<tag> REGISTRY=$USER/ingress-controller make push

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

[k8s-ci-robot]

Welcome @mantuliu!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mantuliu. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aledbf]

/ok-to-test

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@04e2ad8). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #4681   +/-   ##
=========================================
  Coverage          ?   58.65%           
=========================================
  Files             ?       88           
  Lines             ?     6762           
  Branches          ?        0           
=========================================
  Hits              ?     3966           
  Misses            ?     2358           
  Partials          ?      438

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04e2ad8...8a8959c. Read the comment docs.

[sourcelliu]

/assign @aledbf

[aledbf]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, mantuliu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aledbf]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment