From 887e0dae29ebafb587fa8dbe8eb0333a62e76758 Mon Sep 17 00:00:00 2001
From: Jason Antman <jason@jasonantman.com>
Date: Mon, 30 Jul 2018 08:02:33 -0400
Subject: [PATCH] fix markup in CHANGES.rst
---
CHANGES.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/CHANGES.rst b/CHANGES.rst
index ac59d7f9..cc2ce198 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -29,7 +29,7 @@ Some Limits (:py:class:`~.AwsLimit`) now have limits/maxima that are per-resourc
For limits which support different maxima/limit values per-resource, the command line ``awslimitchecker`` script ``-l`` / ``--list-limits`` functionality will now display them in Service/Limit/ResourceID format, i.e.:
-.. code-block::
+.. code-block:: none
Route53/Record sets per hosted zone/foo.com 10000 (API)
Route53/Record sets per hosted zone/bar.com 10000 (API)
@@ -38,7 +38,7 @@ For limits which support different maxima/limit values per-resource, the command
As opposed to the Service/Limit format used for all existing limits, i.e.:
-.. code-block::
+.. code-block:: none
IAM/Groups 300 (API)
IAM/Instance profiles 2000 (API)