From 16db4b38385ddd82653c96186fc5d8f5dae392a8 Mon Sep 17 00:00:00 2001 From: Guillaume Jacquenot Date: Wed, 30 Jul 2025 18:14:48 +0200 Subject: [PATCH 1/3] Update positional_vs_keyword_arguments.ipynb --- source-code/api-design/positional_vs_keyword_arguments.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source-code/api-design/positional_vs_keyword_arguments.ipynb b/source-code/api-design/positional_vs_keyword_arguments.ipynb index 8e9dbdf..e6341bc 100644 --- a/source-code/api-design/positional_vs_keyword_arguments.ipynb +++ b/source-code/api-design/positional_vs_keyword_arguments.ipynb @@ -354,7 +354,7 @@ "id": "9ebb6221-2685-442d-8f7b-c362f755672d", "metadata": {}, "source": [ - "Indeed, why would you bother? Essentially, there are two reaoons:\n", + "Indeed, why would you bother? Essentially, there are two reasons:\n", "1. overhead of function calls, and\n", "1. maintenance." ] From 2e02f4f3bb824d56e807f6e80530907068b0039a Mon Sep 17 00:00:00 2001 From: Guillaume Jacquenot Date: Wed, 30 Jul 2025 18:19:57 +0200 Subject: [PATCH 2/3] Update positional_vs_keyword_arguments.ipynb --- source-code/api-design/positional_vs_keyword_arguments.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source-code/api-design/positional_vs_keyword_arguments.ipynb b/source-code/api-design/positional_vs_keyword_arguments.ipynb index e6341bc..829a978 100644 --- a/source-code/api-design/positional_vs_keyword_arguments.ipynb +++ b/source-code/api-design/positional_vs_keyword_arguments.ipynb @@ -372,7 +372,7 @@ "id": "f08a6028-76e5-486d-a492-191f32815021", "metadata": {}, "source": [ - "The overhead of calling a function with keyword arguments is higher than withoug, as illustrated below." + "The overhead of calling a function with keyword arguments is higher than without, as illustrated below." ] }, { From df8d0d2da027f4906956d72567ca3a2d7ea13f47 Mon Sep 17 00:00:00 2001 From: Guillaume Jacquenot Date: Wed, 30 Jul 2025 18:24:30 +0200 Subject: [PATCH 3/3] Update positional_vs_keyword_arguments.ipynb --- source-code/api-design/positional_vs_keyword_arguments.ipynb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source-code/api-design/positional_vs_keyword_arguments.ipynb b/source-code/api-design/positional_vs_keyword_arguments.ipynb index 829a978..11cf066 100644 --- a/source-code/api-design/positional_vs_keyword_arguments.ipynb +++ b/source-code/api-design/positional_vs_keyword_arguments.ipynb @@ -460,9 +460,9 @@ "id": "56567790-2973-49bb-ab43-ce2e01d6464c", "metadata": {}, "source": [ - "Although keyword arguments are convenient and can make your code more robust since using them reduces the probability of mixing up arguments since you don't have to remember the order, this approach amkes maintaining the functions themselves a bit harder.\n", + "Although keyword arguments are convenient and can make your code more robust since using them reduces the probability of mixing up arguments since you don't have to remember the order, this approach makes maintaining the functions themselves a bit harder.\n", "\n", - "If the caller of the function uses keyword arguments and you change the name of a function argument, the function call will result in a runtime error. The caller will have to adapt her code according to the changes you made.\n", + "If the caller of the function uses keyword arguments and you change the name of a function argument, the function call will result in a runtime error. The caller will have to adapt its code according to the changes you made.\n", "\n", "Calling a function with positional arguments where possible avoids this issue.\n", "\n",