Update README.md (#110)

* Update README.md

Fixed text that described the sample yaml as not having container resource requests, which it does.

* Update README.md

Removing language stating that the referenced yaml doesnt include cpu/memory requests

* Reverting a change from the previous commit

Accidentally removed too many instances of the word 'requests'

README.md

@@ -82,8 +82,8 @@ Consider the following sample pod specification file `pod.yaml`. This file has t
 1. The container in this pod is not running as a read only file system, which could allow it to write to the root filesystem.
 
 **Production readiness:**
-1. The container's CPU requests and limits are not set, which could allow it to consume excessive CPU.
-1. The container's memory requests and limits are not set, which could allow it to consume excessive memory
+1. The container's CPU limits are not set, which could allow it to consume excessive CPU.
+1. The container's memory limits are not set, which could allow it to consume excessive memory
 
    ```yaml
    apiVersion: v1

docs/README.md

@@ -148,10 +148,10 @@ To build KubeLinter from source:
    >   allowing it to write to the root filesystem.
    > 
    > **Production readiness issue**
-   > - The configuration doesn't specify the container's CPU requests and
-   >   limits, allowing it to consume excessive CPU. 
-   > - The configuration doesn't specify the container's memory requests and
-   >   limits, allowing it to consume excessive memory.
+   > - The configuration doesn't specify the container's CPU limits,
+   >   allowing it to consume excessive CPU. 
+   > - The configuration doesn't specify the container's memory limits,
+   >   allowing it to consume excessive memory.
 
 1. To lint this file with KubeLinter, run the following command:
    ```bash