Fixed crates.io badge

Author: Andrew J Westlake

README.md

@@ -2,7 +2,7 @@
 
 [![Actions Status](https://github.com/awestlake87/pyo3-asyncio/workflows/CI/badge.svg)](https://github.com/awestlake87/pyo3-asyncio/actions)
 [![codecov](https://codecov.io/gh/awestlake87/pyo3-asyncio/branch/master/graph/badge.svg)](https://codecov.io/gh/awestlake87/pyo3-asyncio)
-[![crates.io](http://meritbadge.herokuapp.com/pyo3-asyncio)](https://crates.io/crates/pyo3-asyncio)
+[![crates.io](https://img.shields.io/crates/v/pyo3-asyncio)](https://crates.io/crates/pyo3-asyncio)
 [![minimum rustc 1.46](https://img.shields.io/badge/rustc-1.46+-blue.svg)](https://rust-lang.github.io/rfcs/2495-min-rust-version.html)
 
 [Rust](http://www.rust-lang.org/) bindings for [Python](https://www.python.org/)'s [Asyncio Library](https://docs.python.org/3/library/asyncio.html). This crate facilitates interactions between Rust Futures and Python Coroutines and manages the lifecycle of their corresponding event loops.

src/lib.rs

@@ -263,13 +263,13 @@ fn asyncio_get_event_loop(py: Python) -> PyResult<&PyAny> {
 
 /// Get a reference to the Python Event Loop from Rust
 ///
-/// Equivalent to `asyncio.get_running_loop()` in Python 3.7+
+/// Equivalent to `asyncio.get_running_loop()` in Python 3.7+.
 /// > For Python 3.6, this function falls back to `asyncio.get_event_loop()` which has slightly
 /// different behaviour. See the [`asyncio.get_event_loop`](https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.get_event_loop)
 /// docs to better understand the differences.
 pub fn get_running_loop(py: Python) -> PyResult<&PyAny> {
-    // Ideally should call get_running_loop, but calls get_event_loop for compatibility between
-    // versions.
+    // Ideally should call get_running_loop, but calls get_event_loop for compatibility when
+    // get_running_loop is not available.
     GET_RUNNING_LOOP
         .get_or_try_init(|| -> PyResult<PyObject> {
             let asyncio = asyncio(py)?;