From d67a505b13c99acee1c57d945841a06020cea259 Mon Sep 17 00:00:00 2001 From: Ankit Rai Date: Tue, 21 Sep 2021 20:58:52 +0530 Subject: [PATCH] Typo fix --- books/designing-data-intensive-applications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/books/designing-data-intensive-applications.md b/books/designing-data-intensive-applications.md index ca34231..5271194 100644 --- a/books/designing-data-intensive-applications.md +++ b/books/designing-data-intensive-applications.md @@ -225,7 +225,7 @@ If the database itself does not support joins, you have to emulate a join in app The most popular database for business data processing in the 1970s was the IBM's _Information Management System_ (IMS). -IMS used a _hierarchical model_ and like document databases worked well for one-to-many relationships, but it made many-to-,any relationships difficult, and it didn't support joins. +IMS used a _hierarchical model_ and like document databases worked well for one-to-many relationships, but it made many-to-many relationships difficult, and it didn't support joins. #### The network model