From 0ea28c890897a98a7d29fc812a67373030b16dd8 Mon Sep 17 00:00:00 2001 From: Ravi Kalia Date: Thu, 18 Apr 2024 18:06:06 -0500 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 794075b7..6e2b29e6 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,7 @@ Watch [a 15-minute talk](https://iclr.cc/virtual/2022/oral/6603) focused on main - [Documentation](https://einops.rocks/) - [Tutorial](#Tutorials) - [API micro-reference](#API) -- [Why using einops](#Why-using-einops-notation) +- [Why use einops](#Why-use-einops-notation) - [Supported frameworks](#Supported-frameworks) - [Citing](#Citing) - [Repository](https://github.com/arogozhnikov/einops) and [discussions](https://github.com/arogozhnikov/einops/discussions) @@ -200,7 +200,7 @@ Additionally, torch users will benefit from layers as those are script-able and Notation was loosely inspired by Einstein summation (in particular by `numpy.einsum` operation). -## Why use `einops` notation?! +## Why use `einops` notation?! ### Semantic information (being verbose in expectations)