# 5.x — Chapter 5 comprehensive quiz

Quick review

If statements allow us to execute a statement based on whether some condition is true. Else statements execute if the associated if statement is false. You can chain together multiple if and else statements.

Switch statements provide a cleaner and faster method for selecting between a number of discrete items. Switch statements pair great with enumerations.

Goto statements allow the program to jump to somewhere else in the code. Don’t use these.

While loops allow the program to loop as long as a given condition is true. The condition is evaluated before the loop executes.

Do while loops are the same as while loops, but the condition is evaluated after the loop execution. They’re great for menus or things that need to execute at least once.

For loops are the most used loop, and are perfect when you need to loop a specific number of times.

Break statements allow us to break out of a `switch`, `while`, `do while`, or `for` loop. Or a range-based `for` loop, which we haven’t covered yet.

Continue statements allow us to move immediately to the next loop iteration. Be careful when using these with while and do while loops, as your loop counter may not get incremented properly.

And finally, random numbers give us a way to make our programs behave different each time they are run. We’ll see an example of this in the quiz below!

Quiz time!

Warning: The quizzes start getting harder from this point forward, but you can do it. Let’s rock these quizzes!

1) In the chapter 2 comprehensive quiz, we wrote a program to simulate a ball falling off of a tower. Because we didn’t have loops yet, the ball could only fall for 5 seconds.

Take the program below and modify it so that the ball falls for as many seconds as needed until it reaches the ground.

In constants.h:

Show Solution

2a) Implement a game of hi-lo. First, your program should pick a random integer between 1 and 100. The user is given 7 tries to guess the number.

If the user does not guess the correct number, the program should tell them whether they guessed too high or too low. If the user guesses the right number, the program should tell them they won. If they run out of guesses, the program should tell them they lost, and what the correct number is. At the end of the game, the user should be asked if they want to play again. If the user doesn’t enter ‘y’ or ‘n’, ask them again.

Note: You do not need to implement error handling for the user’s guess.

Here’s what your output should look like:

```Let's play a game.  I'm thinking of a number.  You have 7 tries to guess what it is.
Guess #1: 64
Guess #2: 32
Guess #3: 54
Guess #4: 51
Correct! You win!
Would you like to play again (y/n)? y
Let's play a game.  I'm thinking of a number.  You have 7 tries to guess what it is.
Guess #1: 64
Guess #2: 32
Guess #3: 54
Guess #4: 51
Guess #5: 36
Guess #6: 45
Guess #7: 48
Sorry, you lose.  The correct number was 49.
Would you like to play again (y/n)? q
Would you like to play again (y/n)? f
Would you like to play again (y/n)? n
Thank you for playing.
```

Hints:
* If your compiler is C++11 capable, use the Mersenne Twister algorithm from chapter 5.9 -- Random number generation to pick a random number.
* If your compiler is not C++11 capable, you can use rand() (also presented in chapter 5.9 -- Random number generation) to pick a random number
* Write a function that allows the user to play a single game of hi-lo.
* Write a function that asks the user if they want to play again and handles the looping logic for an incorrect input.

Show Solution

2b) Update your previous solution to handle invalid input (e.g. ‘x’) or valid input with extraneous characters (e.g. “43x”) when the user is guessing a number.

Hint: Write a separate function to handle the user inputting their guess (along with the associated error handling).

Show Solution

 6.1 -- Arrays (Part I) Index 5.11 -- Introduction to testing your code

### 689 comments to 5.x — Chapter 5 comprehensive quiz

• kavin

Hi, i was able to solve both the quizzes. Here is my solution for 2a and 2b combined. Let me know if its ok or there is anything i could improve ?

And big thanks for teaching VS debugger in previous lessons, was so helpful in finding my mistakes in this program !

Just saw your quiz answer. Looks like i should have changed lines 67-70 like this ?

• nascardriver

Hey kavin!

Good job using the debugger to find your mistakes! Some suggestions:

- Avoid recursion (A function calling itself) (`getInput` -> `playAgain` -> `getInput` -> ...). Use a loop instead.
- Initialize variables with brace initialization (Line 69).
- Magic number/string: 7. Add a constant.
- Inconsistent formatting. Use your editor's auto-formatting feature (Might be at Edit->Advanced->Format Document).
- Line 84: Should be '.' or ".\n".
- Using `std::exit` can make the control flow harder to understand. Return a `bool` that causes the main loop to stop when the user doesn't want to play anymore.

There's a big quiz coming up in the next chapter, keep it up!

• Mn3m

[code]#include <iostream>
#include <random>
#include <ctime>
#include "constants.h"

void replay();

namespace MyRandom
{

std::mt19937 mersenne{ static_cast<std::mt19937::result_type>(std::time(nullptr)) };
}

int getRandomNumber(int min, int max)
{
std::uniform_int_distribution die{ min, max };
return die(MyRandom::mersenne);
}

void startGame()
{

constexpr int attempts = 7;
std::cout << "Pssss... The correct answer is " << correctAnswer << '\n';//Just for me to verify that everything is alright :)
std::cout << "Let's play a game. I'm thinking of a number. You have "<<attempts<<" tries to guess what it is.\n";
int guess;

for (int i = 1; i <= attempts; i++)
{
std::cout << "Guess# " << i << ':';
std::cin >> guess;

{
std::cout << "Your guess is too high.\n";
}

{
std::cout << "Your guess is too low.\n";
}

else
{
std::cout << "Correct! You won!\n";
replay();
}

}

replay();

}

void replay()
{
char choice;
while (true)
{
std::cout << "Would you like to play again? (y/n)";
std::cin >> choice;

if (choice == 'y')
startGame();
else if (choice == 'n')
{
std::cout << "Thank you for playing.";
exit(0);//Since I keep jumping between startGame() and replay() , the stack is messed up. I had to use exit(0) to terminate instead of a normal return;
}
else
{
std::cin.ignore(32376,'\n');
}

}
}

int main()
{
startGame();
return 0;
} [code]

Can you give me some feedback on this, please ? :)

• Eric

What are the advantages of the one way verses the other?

• nascardriver

Your `calculateHeight` isn't reusable, because it doesn't return the height and doesn't use `secondsPassed`. It also prints the height itself, so you can't use it without printing the height.

Notes:
- Initialize variables with brace initialization.
- Use double literals for doubles (0.0 instead of 0).
- `calculateHeight`'s return value and `secondsPassed` are unused.
- Line 23 doesn't do anything.

`getInitialHeight` and `printHeight` are pretty good, only `calculateHeight` does too much.

• Suyash

My solution (it's working as expected)... You are more than welcome to correct any mistakes that you spot in my code...

• nascardriver

Hi,

Congrats on solving the quiz!

Some suggestions:
- Line 90: In the first iteration, this comparison is unnecessary. Moving the choice check to later or using a do-while loop could fix this.
- Initialize variables with brace initialization for better type safety.
- Magic numbers/strings: 1, 7, 100

• Sinethemba

Hi, I have managed to solve quiz question 2b. Below is my code solution. Any feedback would be highly appreciated.

• nascardriver

Hi!

- Initialize variables with brace initialization (Line 84).
- `user_value != number` in line 49 is always true. If the variables were equal, line 46 would have stopped the loop. You can change the `break` in line 46 to a `return` and move the "Sorry" message to after the loop. That way you don't have to compare the variables in every cycle of the loop.
- `checkUserInput` doesn't check user input. "getUserInput" or similar describes the function better.

The structure of your code is really good, keep it up!

• Sinethemba

Thanks nascardriver!
Your valuable feedback is highly appreciated.

• Limerk

Good Day! I finished reading all tutorials and finally started doing quiz. I would love to hear your criticism and/or suggestions about how I could improve my current solution to the given problem. Thank you in advance!

• nascardriver

Hello!

- Don't use `std::endl` unless you need to.
- Line 17 makes your code non-reusable. It's better to generate the number in a function that you can call in case you want to play multiple games.
- Line 30,31 39,40 45,48: Duplicate code.
- Line 34, 36, 42: Duplicate comparisons. You can use a `while (true)` loop to solve both of these issues.
- Line 99: `(isGuessed && i == tries)` never gets evaluated. The condition stops of `isGuessed` is `true`.
- If your program prints anything, the last thing it prints should be a line feed ('\n').

• Limerk

Thank you so much for your reply! Quick question. I always have duplicate code like in line 30, 31, 39, 40, 45, 48. The one way that I see how I could solve it, I could have created a function that would call this code in the place where I would need it, but this kind of solution seems for me as still a bad practice.... I want your opinion, in cases like this should I try to create a function and use it or it's better to try and change the program flow in order to get rid of these duplicates?

• nascardriver

Replacing these lines with a function is a good start. When you've done that, you'll still have a triple function call. That can happen, but it's an indicator that your control flow might not be the best. Try using a `while (true)` loop as I suggested before, that should get rid of the repetitions entirely. If you're having problems somewhere, please ask.

• Limerk

Ok. Thank you! I'm not afraid of the infinite loop but I didn't want to use it since in the book that I read, "C++ Primer Plus", author suggested that people should try to avoid it. I personally don't think they are too scary, I mean as long as you can terminate it there shouldn't be any problem

• nascardriver

An infinite loops isn't good indeed, but it's better than a repetition. Once you've sorted out your code to remove the repetitions, you good split your code into more functions, making your loop more readable, so it's easy to determine when the loop stops. Maybe you'll find a new termination condition after you cleaned up your code, then the infinite loop is gone too.

• Limerk

Ok, I got it! Thank you once again!

• cnoob

Hi! These tutorials are awesome! Ive just come up with another solution for 2a, and I would be more than happy to have some feedback.

• nascardriver

Hi!

- Magic numbers/strings: 1, 7, 100. Define constants.
- Avoid recursion (A function calling itself). Use a loop instead. (hiLoFunc, playAgain).
- If your program prints anything, the last thing it prints should be a line feed.
- Line 34 always compares true.

• cnoob

Wow, these problems would not have occured to me on my own! Ive just fixed the code according to your remarks. Thank you very much!

• Chandler

I had fun with this one. I cld've done more, made it cleaner and a little more polished, added a header or two, and maybe an enum class.
Thanks to these well-written tutorials, I look forward to jumping out of bed and spending my day learning C++.
Comments and suggestions will be appreciated.

• nascardriver

Congratulations on solving the quiz, I'm glad you're having fun :)

- Compile-time constants should be `constexpr`.
- Don't seed random number generators more than once. You won't get random numbers.
- Line 64 always compares true.
- Line 66+ is unreachable.
- Line 34, 36: Duplicate comparison. Remove line 34, add an `else if` to check for `n`/'N'.
- Use single quotation marks for characters (' ' vs " ").

• Chandler

Thanks for the feedback, nascardriver. I fixed the code and it now works as expected. Thanks.

• chai

hi there, what is your opinion on recursion? People say that recursion is good for code readability but not so good for performance. Is that true?Thanks.

• nascardriver

Many times recursion can be replaced with an equally readable or better readable loop. In certain cases, recursion can be easier to read.
Recursion is bad for performance and suffers from memory exhaustion (There's only a certain number of recursive calls you can make before your program crashes).

Avoid recursion, unless an iterative solution would be a huge mess.

• Daki

Hello!

The code I wrote for 2a is different from the solution above and would appreciate any feedback or criticisms!

• nascardriver

- Magic number/string: 7
- Line 70+: Duplicate comparisons and function calls. You can move the input validation into `contGame` and return a bool from `constGame`.
- Line 31+: Duplicate comparisons. Use nested if-statements.

Your code will be a lot easier to maintain without duplicates. If you have any questions, feel free to ask.

• BakaTensi

What do you think about my solution for 2b? I'm open for criticism. Here are some specific questions I'm concerned about:

-Is my commenting style okay?
-Have I broken down the code into too many or too few functions?
-Is my solution to encase the game variables into a struct and then pass that into functions okay?
-How can I make the random number generation in a way that it's still in a separate function but it doesn't get reseeded every time I start a new game?

As a side note, I've disabled adblock, and it still doesn't show ads, only the place where they are supposed to be.

• nascardriver

> Is my commenting style okay?
Limit lines to 80 characters in length for better readability. This doesn't affect only comments, but also code. Your editor probably has a setting to display a vertical line.
The comments above functions are great. If you think you need a comment inside of a function, you should move the code into a separate function with a good name instead. You can remove your comments in `getUserGuess` and `playAgain` altogether, the code is easy enough.
The comments above `GameVariables` should be above the variable that they refer to to make them easier to find.

> Have I broken down the code into too many or too few functions?
Line 42-46 and 121-125 are identical, they should be moved into a new function. The other functions look good.

> Is my solution to encase the game variables into a struct and then pass that into functions okay?
Yes.

> How can I make the random number generation in a way that it's still in a separate function but it doesn't get reseeded every time I start a new game?
`static` (Lesson S.4.3)

- Line 30, 31: `return { /* ... */ }` allows for better optimization.
- Line 36+ and 115+: Use a `while (true)` loop. A `do-while` loop makes the reader expect some condition at the end.

Looks good overall :)

• BakaTensi

Thank you very much for the feedback!

• Ethan

• nascardriver

- Line 47: Initialize with brace initialization.
- Line 57 is always true. Should be just `else`.
- Magic numbers/strings: 1, 7, 100

Looks good otherwise :)

What do you think?

• nascardriver

- Initialize your variables with brace initializers.
- Magic number/string: 7
- Use ++prefix unless you need postfix++.
- Line 59: Nice conditional operator!
- Avoid static duration variables. They'll break your code when you get to object oriented programming or threading.

Thanks a lot!

• JamesWeb

Hello, I have a question.
Doesn't number and answer get created and destroyed each iteration?
So I thought if it would be better to put them outside of the while loop?
Also is there anything else in my code that I could improve or change?

• nascardriver

- Initialize your variables with brace initializers.
- Seed random number generators only once. `getRandomNumber` isn't random.
- Line 55: You don't need this variable, you can call `isGuesCorrect` in the if-statement.
- Line 77, 78: Duplicate comparison of `answer` to 'y'.
- Compile-time constants should be `constexpr`.

> Doesn't number and answer get created and destroyed each iteration?
No, your computer uses variables that never get created and never get destroyed, they're there all the time. Those variables are re-used across functions.

• Shawn

Hello, I wrote the answer to 2a) in a different way than you wrote. can you check this please? thanks.

#include <iostream>
#include <random>
#include <ctime>

enum class GuessRespnse
{
SUCCESS,
FAILURE,
};

int getRandom(int min, int max)
{

static std::mt19937 mersenne(static_cast<std::mt19937::result_type>(std::time(nullptr)));
std::uniform_int_distribution<> range(min, max);
return range(mersenne);

}

int takeGuess(int guessID)
{
std::cout << "Guess #" << guessID << ": ";
int guess;
std::cin >> guess;

return guess;
}

{
while (true) //loop until user enters a vaild input
{
std::cout << "Would you like to play again(y / n) ? ";
char another;
std::cin >> another;

std::cin.ignore(32767, '\n');

if (another == 'y' || another == 'n')
return another == 'y';
}
}

//Check if the guess of the user is correct and return it by "GuessRespnse" enum
GuessRespnse guessResponsing(int theRandom, int theGuess)
{
if (theRandom == theGuess)
{
std::cout << "Correct!You win!\n";
return GuessRespnse::SUCCESS;
}

std::cout << "Your guess is too " << (theGuess < theRandom ? "low" : "high") << ".\n";
return GuessRespnse::FAILURE;
}

//return if the user wants to play again
bool playGame(int tries = 7, int min = 0, int max = 10)
{
std::cout << "Let's play a game. I'm thinking of a number. You have 7 tries to guess what it is\n";

int random = getRandom(min, max);

for (int count = 0; count < tries; count++)
{
int guess{ takeGuess(count) };

if (guessResponsing(random, guess) == GuessRespnse::SUCCESS)
{
return true;
return false;
}
}
}

int main()
{
while (playGame());
}

• nascardriver

Hi!

Please use code tags when posting code.

- Initialize your variables with brace initializers.
- Don't pass 32767 to `std::cin.ignore`. Pass `std::numeric_limits::max()`. Passing 32767 has no special meaning.
- Line 39, 40: Duplicate comparison of `another` to 'y'.
- Line 53: Nice.
- Magic number/string: 7.
- Use ++prefix unless you need postfix++.

A lot of code editors offer a spell checker, see if you can get one.

• Shawn

1)I didn't understand if you mean to the initializing in the for loop or when I initialized variables(if I remember correctly at the beginning of the tutorial you recommended to initialize a variable only when you will use his value).
4) thanks (:
5) how do you recommend to do that?
6) yeah, visual studio makes for loop automatically(for + tab + tab) and i didn't notice.
7) lol

• nascardriver

Line 14, 15, 63 and 65 should use brace initialization.
If you know that you're going to write to a variable before using it, you can omit the initialization. Initializing the anyway (To their default value, ie. empty curly braces) can help preventing hard-to-find errors.

• Muirgheal Wen

Hi Alex & nascardriver! Thanks for looking over so many people's code- I did a first pass at the solution myself, then checked against the provided solution, and looked over the comments you provided below.
There were a few places where my solution and the provided one differs in terms of where we chose to put functions. I've marked them as comments below.
Here's my solution for the Hi-Lo game.

• - Initialize your variables with brace initializers.
- Limit your lines to 80 characters in length for better readability.
- Use `constexpr` for compile-time constants.
- There's no reason to use `std::atoi` here. `std::cin >>` is fully capable of integer extraction.
- Inconsistent formatting. Use your editor's auto-formatting feature.
- Line 47 is always `true`.
- Use ++prefix unless you need postfix++.
- Line 84, 86, 89: Triple comparison of `play_again_switch` to `userQuit`. All three comparisons produce the same value. Line 86+ can be moved out of the loop.

I don't understand your first comment. Can you tell me which line numbers of the solution and your code you're referring to?

Configuring the game in `manager` is fine.

• Parsa

What is the difference between using if multiple times rather than using if once and then else if?

And here is my hilo solution-

• - Initialize your variables with brace initializers.
- Limit your lines to 80 characters in length for better readability.
- Don't use `goto`. Loops are easier to read.
- Inconsistent formatting. Use your editor's auto-formatting feature.
- Magic number/string: 7.
- Seed random number generators only once.
- Don't use `std::exit`.
- Use ++prefix unless you need postfix++.
- Line 63 always evaluates to true.
- Line 28+, 45+: Duplicate code.
- Line 41: `guess != randomNumber` is always true.

• Parsa

-I don't understand what I am supposed to do with the magic number 7.

-Line 41 and 63: don't understand how it always evaluates to true.

Thank you by the way.

• > I don't understand what I am supposed to do with the magic number 7
Add a `constexpr` variable and use that wherever you used 7.

> don't understand how it always evaluates to true
Line 41
The check only runs if line 24 was `false`. If line 24 was false, then you already know that `guess != randomNumber`.

Line 63
You know `!(guess == randomNumber)` because of line 24.
You know `!(guess < randomNumber)` because of line 59.
The only relation that the two variables could have is `guess > randomNumber`.

• Parsa

Okay makes sense. Thanks.

• Parsa

When would it be better to use operator= versus brace initialization? Since they seem to be able to do different things.

• https://www.learncpp.com/cpp-tutorial/5-x-chapter-5-comprehensive-quiz/comment-page-8/#comment-423263

• `operator=` is used for assignments. I suppose you mean copy initialization.

Always use brace initialization unless you can't (Because of `std::initializer_list`. Covered later).

• alfonso

My hi-lo solution:

main.cpp

functions.cpp

functions.h

globals.h

• - Initialize your variables with brace initializers.
- Limit your lines to 80 characters in length for better readability.
- Don't pass 32767 to `std::cin.ignore`. Pass `std::numeric_limits<std::streamsize>::max()`.
- `tooHigh`, `tooLow`, `itMatches`: That's what enums are there for.
- functions.cpp:58+ and `guess`: You didn't gain anything from adding `guess`.
- Use `switch` for limited sets of values.
- functions.cpp:36,37: `std::swap`.
- functions.cpp:46 Good use of the constant!
- `userNumber` and `match` should be declared inside of the loop.
- functions.cpp:84,85: Why do you assume an error when the input wasn't 'y' or 'n', but when the input is 'y' or 'n', you're sure there is no trailing input?
- `seed` isn't a seed, it's a mersenne twister. The seed is the part you're initializing `seed` with.
- You're using the same name style for variables and functions, this can lead to confusion.

• alfonso

> - Use `switch` for limited sets of values.

I wanted to use keywords like break and continue inside the for loop, but depending on switch cases. So then break would apply to switch statement. Using if statement instead, I do not need to have care about conflicts using brake inside a switch inside a loop.

> `userNumber` and `match` should be declared inside of the loop.

I deleted match, and guess() function and tooHigh, tooLow global constants. Why I declared variables outside the loop: for performance reasons. Making the variable outside means making the variable once and then only assigning values in the loop for it. I braked the rule 'smallest scope as possible'.

Btw, I can win this game every time. :) If you choose right, at 6th move, you'll have two 'moves' and only two possible answers.

• > switch
functions.cpp:79+ Doesn't use `break` or `continue`.

> Making the variable outside means making the variable once and then only assigning values in the loop for it
This can be a valid argument for custom types, but not for fundamental types. The space of the variable is re-used, there is not creation or destruction of fundamental types. You're increasing the scope without gaining anything from it.

> If you choose right, at 6th move, you'll have two 'moves' and only two possible answers.
Good observation! This reminds me of a problem with an egg and a skyscraper. If you get into algorithms, you're bound to run into it.

• Parsa

This code won't compile ( I know my function and variable names aren't great and aren't consistent)

• Always post error messages along with their line numbers.

Brace initialization enforces fairly strict conversion rules. You can't initialize a `double` from an `int`. Add a `static_cast<double>`. Change the `2` in your `distanceFallen` calculations to a `2.0`. `2` is an integer, `2.0` is a `double`.

• samtheham

Hi Alex/Nascardriver! Thanks again for all the fantastic work on this site. If you could help me look over my code (Q2b) and let me know what improvements can be made, it would be greatly appreciated. My approach for the loops was a bit different from your solution, relying mostly on infinite loops and breaks rather than for statements. I do this mostly because I personally find it easier to follow the logic, but if there's good reason to use for statements instead, I'd appreciate the pointer. (Oh and I use #pragma once because I'm really lazy to type header guards for exercises, sorry) Code as follows:

main.cpp:

input.h:

input.cpp:

random.h:

random.cpp:

playagain.h:

playagain.cpp:

• - Limit your lines to 80 characters in length for better readability.
- Initialize your variables with brace initializers.
- Don't pass 32767 to @std::cin.ignore. Pass @std::numeric_limits<std::streamsize>::max().
- Use `switch` for a limited set of values.
- Use `constexpr` for compile-time constants.
- input.cpp:18 isn't guarded by the `else`. Use your editor's auto-formatting feature, braces for `if`s, and enable warnings.
- Magic string: 7.
- "main.cpp" has a bunch of unnecessary includes.
- main.cpp:29 always compares `true`.

> good reason to use for statements
Use what shows your intentions best. Doing so improves readability and allows the compiler to apply appropriate optimizations. `for` doesn't "leak" its iteration and (if you don't use `break`) it's easy to see when it will stop. If you use an infinite loop instead, the read has to read through the entire loop's body to see how long the loop will run.

• samtheham

• Samira Ferdi

Hi, Alex and Nascardriver!

This is my quiz no. 2. What do you think?

I wanna ask about something inside checkHiLoNumber(). In the else statement I write

We know what is the case of else statement by looking other statements above else statement (if and elseif): userGuessNumber == matchNumber. I wanna know your opinion. Should I give the else statement an independent context like

so, we know explicitly every checking statement. I'm glad to hear yours! Thanks a lot!

• Uhh, it started very good, then came `main`.

- Line 40 has no effect. You don't need to `return` from `void`s and there's no code after this line.
- Line 81, 81, 97: Magic strings/number: 1, 7, 100.
- Line 72 should be moved into the loop. Then you don't need line 97.
- Line 91 always compares true. You're not ending the game when the player won.

> Should I give the else statement an independent context like
No, that'd be wasted performance. There are types where (a < b) (b < a) (a == b) can all be false at the same time, `int` isn't one of them. If your conditional code is getting too long, you should add a comment to the `else`, saying that this is the case where (userGuessNumber == matchNumber), but don't check for it.

• Samira Ferdi

Thanks for the good feedback, Nascardriver!
So, this is my change:

1. I change all int type to short because I think short is the best fit data type (the number is very small - between 1 and 100). I'm thinking to make all my variable unsigned (except may be all variable that used in loop). What do you think about this?

2. I delete checkHiLoNumber(). I move checking guessing thing in main function for performance reason

3. main()

• 1. Use `int` unless you have special needs. If you have special needs, use `std::int_fast*_t` or `std::int_least*_t`. Don't use `unsigned`, see lesson 4.5.

2. You're not gaining any performance from putting everything into one function. All you did was make the code less readable and reusable.

• Samira Ferdi

Thank you, Nascardriver for your correction!

This is my change!