diff --git a/docs/creating_platform_code_review.md b/docs/creating_platform_code_review.md
index ab931fbd..36c5171d 100644
--- a/docs/creating_platform_code_review.md
+++ b/docs/creating_platform_code_review.md
@@ -52,7 +52,7 @@ PLATFORM_SCHEMA = PLATFORM_SCHEMA.extend({
  2. Group your calls to `add_devices` if possible.
  3. If the platform adds extra services, the format should be `<domain of your integration>.<service name>`. So if your integration's domain is "awesome_sauce" and you are making a light platform, you would register services under the `awesome_sauce` domain. Make sure that your services [verify permissions](auth_permissions.md#checking-permissions).
 
-### 5. Entity
+### 4. Entity
 
  1. Extend the entity from the integration you're building a platform for.
 
@@ -69,7 +69,7 @@ PLATFORM_SCHEMA = PLATFORM_SCHEMA.extend({
  5. When dealing with time, state and/or attributes should not contain relative time since something happened. Instead, it should store UTC timestamps.
  6. Leverage the [entity lifecycle callbacks](entity_index.md#lifecycle-hooks) to attach event listeners or clean up connections.
 
-### 4. Communication with devices/services
+### 5. Communication with devices/services
 
  1. All API specific code has to be part of a third party library hosted on PyPi. Home Assistant should only interact with objects and not make direct calls to the API.