From 581c43f25c8364765aa2c909425cc944d109d1a3 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Tue, 1 Nov 2022 21:46:29 -0400 Subject: [PATCH] spelling: member Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- doc/1A_on_performance.qbk | 2 +- .../boost_optional/tutorial/performance_considerations.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/1A_on_performance.qbk b/doc/1A_on_performance.qbk index 968b18f..f254f09 100644 --- a/doc/1A_on_performance.qbk +++ b/doc/1A_on_performance.qbk @@ -86,7 +86,7 @@ Which gives us the following layout (and smaller total size): [$images/opt_align3.png] -Sometimes it requires detailed consideration what data we make optional. In our case above, if we determine that both minimum and maximum value can be provided or not provided together, but one is never provided without the other, we can make only one optional memebr: +Sometimes it requires detailed consideration what data we make optional. In our case above, if we determine that both minimum and maximum value can be provided or not provided together, but one is never provided without the other, we can make only one optional member: struct Limits { diff --git a/doc/html/boost_optional/tutorial/performance_considerations.html b/doc/html/boost_optional/tutorial/performance_considerations.html index 975a738..f6e7fb4 100644 --- a/doc/html/boost_optional/tutorial/performance_considerations.html +++ b/doc/html/boost_optional/tutorial/performance_considerations.html @@ -165,7 +165,7 @@ Sometimes it requires detailed consideration what data we make optional. In our case above, if we determine that both minimum and maximum value can be provided or not provided together, but one is never provided without the - other, we can make only one optional memebr: + other, we can make only one optional member: 

struct Limits
 {