diff --git a/Cargo.toml b/Cargo.toml
index 6693d232..d760f358 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -30,8 +30,7 @@ version = "0.2"
 default-features = false
 
 [dependencies.ndarray]
-version = "0.11.2"
-git = "https://github.com/bluss/ndarray"
+version = "0.12"
 features = ["blas"]
 default-features = false
 
diff --git a/README.md b/README.md
index f9077263..e6ba61a2 100644
--- a/README.md
+++ b/README.md
@@ -24,8 +24,8 @@ There are two ways to link LAPACKE backend:
 There are three features corresponding to the backend implementations (`openblas` / `netlib` / `intel-mkl`):
 
 ```toml
-[depencdencies]
-ndarray = "0.11"
+[dependencies]
+ndarray = "0.12"
 ndarray-linalg = { version = "0.9", features = ["openblas"] }
 ```
 
@@ -34,8 +34,8 @@ For the sake of linking flexibility, you can provide LAPACKE implementation (as
 You should link a LAPACKE implementation to a final crate (like binary executable or dylib) only, not to a Rust library.
 
 ```toml
-[depencdencies]
-ndarray = "0.11"
+[dependencies]
+ndarray = "0.12"
 ndarray-linalg = "0.9"
 openblas-src = "0.5" # or another backend of your choice
 
@@ -53,8 +53,8 @@ extern crate openblas_src; // or another backend of your choice
 If you creating a library depending on this crate, we encourage you not to link any backend for flexibility:
 
 ```toml
-[depencdencies]
-ndarray = "0.11"
+[dependencies]
+ndarray = "0.12"
 ndarray-linalg = { version = "0.9", default-features = false }
 ```