Markdown indentation

Author: joemsak

README.md

@@ -60,41 +60,42 @@ github:
 
 1) You can now use the following API to get GitHub information about that team:
 
-  ```ruby
-  team = CodeTeams.find('My Team')
-  members = team.github.members
-  github_name = team.github.team
-  ```
+    ```ruby
+    team = CodeTeams.find('My Team')
+    members = team.github.members
+    github_name = team.github.team
+    ```
 
-  Alternatively, you can assign an accessor method name that differs from the plugin's class name:
+    Alternatively, you can assign an accessor method name that differs from the plugin's class name:
 
-  ```ruby
-  class MyPlugin < CodeTeams::Plugin
-    data_accessor_name :other_name
+    ```ruby
+    class MyPlugin < CodeTeams::Plugin
+      data_accessor_name :other_name
 
-    def other_name
-      # ...
+      def other_name
+        # ...
+      end
     end
-  end
 
-   # You can then use:
-   team.other_name
-   # similarly to the Github example above
-   # You can then access data in the following manner:
-   team.other_name.attribute_name
-   ```
+    # You can then use:
+    team.other_name
+    # similarly to the Github example above
+    # You can then access data in the following manner:
+    team.other_name.attribute_name
+    ```
 
-   However, to avoid confusion, it's recommended to use the naming convention 
-   whenever possible so that your accessor name matches your plugin's name
+    However, to avoid confusion, it's recommended to use the naming convention 
+    whenever possible so that your accessor name matches your plugin's name
 
 2) Running team validations (see below) will ensure all teams have a GitHub team specified
 
-Your plugins can be as simple or as complex as you want. Here are some other things we use plugins for:
-- Identifying which teams own which feature flags
-- Mapping teams to specific portions of the code through `code_ownership`
-- Allowing teams to protect certain files and require approval on modification of certain files
-- Specifying owned dependencies (Ruby gems, JavaScript packages, and more)
-- Specifying how to get in touch with the team via Slack (their channel and handle)
+    Your plugins can be as simple or as complex as you want. Here are some other things we use plugins for:
+
+    - Identifying which teams own which feature flags
+    - Mapping teams to specific portions of the code through `code_ownership`
+    - Allowing teams to protect certain files and require approval on modification of certain files
+    - Specifying owned dependencies (Ruby gems, JavaScript packages, and more)
+    - Specifying how to get in touch with the team via Slack (their channel and handle)
 
 ## Configuration
 You'll want to ensure that all teams are valid in your CI environment. We recommend running code like this in CI: