fix pod =item for html

README.md

@@ -40,13 +40,21 @@ If the limits has exceeded then REG.API sets the error code (depends on kind of)
 
 The following tips are there might helps to reduce the possibility of being rate limited:
 
-- Store all domain name or service related data locally and use the REG.API in cases you want to change some data in
-the registry (e.g. contact data, DNS servers, etc).
-- Group similar items and execute a bulk API request. A bunch of methods supports sending request for the list of items at
-the same time (e.g. multiple domain names). Check the details at
-[REG.API Service list identification parameters](https://www.reg.com/support/help/API-version2\#inputparams\_identification\_multi).
-- Keep the logs of interactions with REG.API (requests and responses). This will helps quickly resolve the issues
-instead of sending additional requests to find out what's happened.
+- __Caching__
+
+    Store all domain name or service related data locally and use the REG.API in cases you want to change some data in
+    the registry (e.g. contact data, DNS servers, etc).
+
+- __Bulk requests__
+
+    Group similar items and execute a bulk API request. A bunch of methods supports sending request for the list of items at
+    the same time (e.g. multiple domain names). Check the details at
+    [REG.API Service list identification parameters](https://www.reg.com/support/help/API-version2\#inputparams\_identification\_multi).
+
+- __Journaling__
+
+    Keep the logs of interactions with REG.API (requests and responses). This will helps quickly resolve the issues
+    instead of sending additional requests to find out what's happened.
 
 ## Categories (namespaces)
 

lib/Regru/API.pm

@@ -117,14 +117,20 @@ The following tips are there might helps to reduce the possibility of being rate
 
 =over
 
-=item Store all domain name or service related data locally and use the REG.API in cases you want to change some data in
+=item B<Caching>
+
+Store all domain name or service related data locally and use the REG.API in cases you want to change some data in
 the registry (e.g. contact data, DNS servers, etc).
 
-=item Group similar items and execute a bulk API request. A bunch of methods supports sending request for the list of items at
+=item B<Bulk requests>
+
+Group similar items and execute a bulk API request. A bunch of methods supports sending request for the list of items at
 the same time (e.g. multiple domain names). Check the details at
 L<REG.API Service list identification parameters|https://www.reg.com/support/help/API-version2#inputparams_identification_multi>.
 
-=item Keep the logs of interactions with REG.API (requests and responses). This will helps quickly resolve the issues
+=item B<Journaling>
+
+Keep the logs of interactions with REG.API (requests and responses). This will helps quickly resolve the issues
 instead of sending additional requests to find out what's happened.
 
 =back