Skip to content

Commit 63d9f89

Browse files
committed
Fix image links
1 parent 45fd110 commit 63d9f89

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ It is written by the same author, and published by the fine folks at objc.io.
9191
Buying a copy of the book is not only a nice way to support this project, it also gets you something quite interesting to read.
9292
Win-win!
9393

94-
[![Optimizing Collections (eBook)](OptimizingCollections.png)][OptimizingCollections]
94+
[![Optimizing Collections (eBook)](docs/images/OptimizingCollections.png)][OptimizingCollections]
9595

9696
[OptimizingCollections]: https://www.objc.io/books/optimizing-collections/
9797

@@ -157,7 +157,7 @@ For example, using a single array to hold a sorted list of items has quite horri
157157
complexity when there are many elements. However, up to a certain maximum size, a simple array is in fact
158158
the most efficient way to represent a sorted list.
159159

160-
![Typical benchmark results for sorted collections](http://lorentey.github.io/BTree/images/Sorted%20Collections%20in%20Swift.png)
160+
![Typical benchmark results for sorted collections](docs/images/Sorted%20Collections%20in%20Swift.png)
161161

162162
The benchmark above demonstrates this really well: insertion of *n* elements into a sorted array
163163
costs O(n^2) when there are many items, but for many reasonably sized data sets, it is still much faster

0 commit comments

Comments
 (0)