Use BSD3 license

README.md

@@ -1,7 +1,7 @@
 [![CI](https://github.com/bluesky/ophyd-async/actions/workflows/ci.yml/badge.svg)](https://github.com/bluesky/ophyd-async/actions/workflows/ci.yml)
 [![Coverage](https://codecov.io/gh/bluesky/ophyd-async/branch/main/graph/badge.svg)](https://codecov.io/gh/bluesky/ophyd-async)
 
-[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+[![License](https://img.shields.io/badge/License-BSD_3--Clause-blue.svg)](https://opensource.org/licenses/BSD-3-Clause)
 
 # ophyd_async
 
@@ -10,10 +10,10 @@ Asynchronous Bluesky hardware abstraction code, compatible with control systems
 This is where you should write a short paragraph that describes what your module does,
 how it does it, and why people should use it.
 
-Source          | <https://github.com/bluesky/ophyd-async>
-:---:           | :---:
-Documentation   | <https://bluesky.github.io/ophyd-async>
-Releases        | <https://github.com/bluesky/ophyd-async/releases>
+|    Source     |     <https://github.com/bluesky/ophyd-async>      |
+| :-----------: | :-----------------------------------------------: |
+| Documentation |      <https://bluesky.github.io/ophyd-async>      |
+|   Releases    | <https://github.com/bluesky/ophyd-async/releases> |
 
 This is where you should put some images or code snippets that illustrate
 some relevant examples. If it is a library then you might put some