From d8d7df6f545101ea34ca6e2b7f2584ece28adfaf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Luis=20Rojas=20Aragon=C3=A9s?= <crojasaragonez@hotmail.com> Date: Wed, 26 Feb 2020 11:35:20 -0600 Subject: [PATCH] Fix Typo --- docs/master/eloquent/nested-mutations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/master/eloquent/nested-mutations.md b/docs/master/eloquent/nested-mutations.md index 4307035d2f..ea1eb94375 100644 --- a/docs/master/eloquent/nested-mutations.md +++ b/docs/master/eloquent/nested-mutations.md @@ -65,7 +65,7 @@ A nested `BelongsTo` relationship exposes the following operations: - `create` a new related model and attach it - `update` an existing model and attach it - `upsert` a new or an existing model and attach it -- `diconnect` the related model +- `disconnect` the related model - `delete` the related model and the association to it Both `disconnect` and `delete` don't make much sense in the context of an update.