fixed formating issues with rst

docsite/rst/porting_guide_2.0.rst

@@ -58,10 +58,9 @@ uses key=value escaping which has not changed.  The other option is to check for
 * porting task includes
 * More dynamic. Corner-case formats that were not supposed to work now do not, as expected.
 * variables defined in the yaml dict format https://github.com/ansible/ansible/issues/13324
- * variable precedence
 * templating (variables in playbooks and template lookups) has improved with regard to keeping the original instead of turning everything into a string.
   If you need the old behavior, quote the value to pass it around as a string.
- Empty variables and variables set to null in yaml are no longer converted to empty strings. They will retain the value of `None`.
+* Empty variables and variables set to null in yaml are no longer converted to empty strings. They will retain the value of `None`.
   You can override the `null_representation` setting to an empty string in your config file by setting the `ANSIBLE_NULL_REPRESENTATION` environment variable.
 * Extras callbacks must be whitelisted in ansible.cfg. Copying is no longer necessary but whitelisting in ansible.cfg must be completed.
 * dnf module has been rewritten. Some minor changes in behavior may be observed.
@@ -72,9 +71,9 @@ Deprecated
 
 While all items listed here will show a deprecation warning message, they still work as they did in 1.9.x. Please note that they will be removed in 2.2 (Ansible always waits two major releases to remove a deprecated feature).
 
-* Bare variables in with_ loops should instead use the “{{var}}” syntax, which helps eliminate ambiguity.
+* Bare variables in `with_` loops should instead use the “{{var}}” syntax, which helps eliminate ambiguity.
 * The ansible-galaxy text format requirements file. Users should use the YAML format for requirements instead.
-* Undefined variables within a with_ loop’s list currently do not interrupt the loop, but they do issue a warning; in the future, they will issue an error. 
+* Undefined variables within a `with_` loop’s list currently do not interrupt the loop, but they do issue a warning; in the future, they will issue an error.
 * Using variables for task parameters is unsafe and will be removed in a future version. For example::
 
     - hosts: localhost
@@ -125,7 +124,6 @@ Porting plugins
 
 In ansible-1.9.x, you would generally copy an existing plugin to create a new one. Simply implementing the methods and attributes that the caller of the plugin expected made it a plugin of that type. In ansible-2.0, most plugins are implemented by subclassing a base class for each plugin type. This way the custom plugin does not need to contain methods which are not customized.
 
-.. note::
 
 Lookup plugins
 --------------