# data[].attributes.headline
3. things you learned during our proofs activities are.... 2. questions you still have about proofs are.... 1. thing our team did really well today was...

# data[].attributes.subject
3. things you learned during our proofs activities are.... 2. questions you still have about proofs are.... 1. thing our team did really well today was...

# data[].attributes.body
I’ve learned that proving lines are parallel are very important when it comes to finding angles on lines it has also helped me understand the concept of Converses. I really dont have any questions on this topic and one thing my team did really well was work together

# data[].attributes.headline
1. You don't always need to use a lot of steps 2. You have to write words in math. 3. Proofs require logical thinking

# data[].attributes.subject
1. You don't always need to use a lot of steps 2. You have to write words in math. 3. Proofs require logical thinking

# data[].attributes.body
1.  Is evidence ever in the form of an equation or is it always words?
3. My team did a good job with time management.

# data[].attributes.headline
Savannah Bennett: 1. you can solve large proofs with minimal evidence, how to use all the different converses, how to insert special characters for math  

# data[].attributes.subject
Savannah Bennett: 1. you can solve large proofs with minimal evidence, how to use all the different converses, how to insert special characters for math  

# data[].attributes.body
2. I don't have any questions I just need to keep practicing them
3. my team worked together efficiently

# data[].attributes.body
- what a proof is
- how to make a reason to proofs
-----------------------------------------------------
- don't have questions
-----------------------------------------------------
-join the meeting

# data[].attributes.headline
3. I learned what a proof was,  how to determine which reason to use for a proof, and to write the given reasons first. 2. I don't have any questions. 1. My team was really good at communicating.

# data[].attributes.subject
3. I learned what a proof was,  how to determine which reason to use for a proof, and to write the given reasons first. 2. I don't have any questions. 1. My team was really good at communicating.

# data[].attributes.body
1. How to use the converse
2.I didnt have to use all of the squares when writing proofs
3. Always state the given first
1. how do i know how to prove the next slide
2. what is the point of doing proofs
1.we used our time efficiently

# data[].attributes.headline
1. Our team did a good job talking over every step in the proofs.                                        2. I get confused on which evidence I need sometimes.  3. I learned that there are many different ways to solve proofs.  

# data[].attributes.subject
1. Our team did a good job talking over every step in the proofs.                                        2. I get confused on which evidence I need sometimes.  3. I learned that there are many different ways to solve proofs.  

# data[].attributes.body
1.  Communicating
2.
3. How to use less evidence to solve larger proofs,

# data[].attributes.headline
1. how to prove if a statement is correct with a few given statements

# data[].attributes.subject
1. how to prove if a statement is correct with a few given statements

# data[].attributes.body
2. you don't have to fill out the entire box and that you can solve something with only a couple statements
3.

# data[].attributes.headline
1. I  learned how to solve proofs and what they are. 

# data[].attributes.subject
1. I  learned how to solve proofs and what they are. 

# data[].attributes.body
2. I am sometimes confused about the converse.
3. Not sure what my team did well, just pretty average team stuff.

# data[].attributes.headline
3. You are able to solve large proofs with just a couple pieces of evidence. 2. Sometimes I'm not sure exactly what the evidence is supposed to be. 1. We communicated and were able to move as a group.

# data[].attributes.subject
3. You are able to solve large proofs with just a couple pieces of evidence. 2. Sometimes I'm not sure exactly what the evidence is supposed to be. 1. We communicated and were able to move as a group.

# data[].attributes.body
there is a right and wrong way to do proofs
but a lot of things are acceptable
the reasons have to be detailed like you have to be able to prove it
2.im still bad at proofs because i need to study rules more so is there anything other way you can explain it and  what is the point?
1. my group still has great communication and has since we started.

# data[].attributes.headline
1. how to solve proofs with little evidence. 

# data[].attributes.subject
1. how to solve proofs with little evidence. 

# data[].attributes.body
2.  how to use the different converses to solve problems.
3. How to use special characters
1. Will there always be at least one given thing?
2. How do you know exactly what reason to put if there is a lot of lines and angles?
1. Proof reading thoroughly.

# data[].attributes.headline
3. how to use special characters, i learned how use evidence to prove math solutions, i learned how to use different converses.

# data[].attributes.subject
3. how to use special characters, i learned how use evidence to prove math solutions, i learned how to use different converses.

# data[].attributes.body
2. i have no questions.
1. We problem solved well

# data[].attributes.body
3. what a proof is, just write given for first, how to solve a proof
2.  how do different proofs go together, is there always a given
3. we worked very well on talking and working together

# data[].attributes.headline
3. things i leaned is how to find the measure of a slope and proof. 

# data[].attributes.subject
3. things i leaned is how to find the measure of a slope and proof. 

# data[].attributes.body
2. don't have any.
1. worked together like team work and discussed our opinion on the problem.

# data[].attributes.body
1. I learned what a proof was and what its used for
2. How to use little evidence to solve proofs
3. Different properties and what they mean

1. Do you always have to have so many reasons?
2. When will we use proofs in real life?

1. My team worked well to finish on time today

# data[].attributes.headline
3. First statements are the givens, last statement in what you are proving, converse can be reasons

# data[].attributes.subject
3. First statements are the givens, last statement in what you are proving, converse can be reasons

# data[].attributes.body
2. How do the proofs lead into one another? How do you prove the last statement effectively?
1. Fixing first set of proofs

# data[].attributes.body
1.Some proofs take more steps then others.
2.Why do you add the word converse after you say the type of angle relationship?
3.My team did good we got through the questions.

# data[].attributes.body
1. I learned what a proof was and how we can use the to prove things in a transversal
2. Can you connect different proofs?
3. My team worked good together

# data[].attributes.headline
to make sure you write the symbols correctly 

# data[].attributes.subject
to make sure you write the symbols correctly 

# data[].attributes.body
having your reasons match your statement

there is a right and wrong way to do proofs

2. -Are there going to be more terms when doing proofs
- why are they so complicated

1. My group (me and nancy) did talk a lot more 😼

# data[].attributes.headline
3. what a proof is, there are going to be different ways to solve proofs, and put givens first

# data[].attributes.subject
3. what a proof is, there are going to be different ways to solve proofs, and put givens first

# data[].attributes.body
2.  will there always be a given
1. communication

# data[].attributes.body
2. How to solve and explain proofs
3.People can have different answers to proofs

# data[].attributes.body
3. do givens first
2.i don’t have any
1. work together

# data[].attributes.body
1. how to use converses to determine other angles, you have to write down the givens first, and there are many different ways to prove a statement.
2. dont really have any questions
3. worked together effectively

# data[].attributes.headline
   3. You can prove something using the slope. The slope can help you.

# data[].attributes.subject
   3. You can prove something using the slope. The slope can help you.

# data[].attributes.body
2. You can solve a statement with little proof
1. how to use the congruent symbol and the equal sign correctly in a statement

2. Can you connect one proof to another one?
1. Is it possible to find a proof in other ways? By that I mean is there more than one way to do this?

1. we corrected a few mistakes well  today

- Kaitlyn

# data[].attributes.body
1. how to find the measure of a slope, how to explain proofs, and to put givens first
2. i dont have any
3. we agreed with each other easily

# data[].attributes.body
3) I've learned what is a proof, how to proof.
2) none
1) communicating, and helping each other

# data[].attributes.body
1. That our team works very well together, if slopes are positive or negative, and how to find the slope.
2. No real questions
3. We communicated and got started quickly very well.

# data[].attributes.body
1. I learned that there are more ways in which you can prove that lines are parallel, there are multiple methods that you can use to prove, and how much you can do with angle relations.
2. Can two lines only be proven as parallel if they are given or if they share alternate and consecutive angles?
3. My group was on task today, and we completed our work efficiently.

# data[].attributes.body
3. To always list your givens first, to use congruent symbol when dealing with angles, and use the m when comparing the angles measures
2. Are proofs always used to compare angles? Will proofs be a big part of the Unit 1 test?
1. Communicating about other classes that we have besides geometry.

# data[].attributes.body
1. What made slopes perpendicular and parallel.
2. Transverse identity
3. The slope is rise over run.
4. No questions
5. Communicated and agreed well.

# data[].attributes.body
3. there are many different ways to write proofs, you always have to write the givens, and what the transitive property is.
2. what if you don't fill up all of the slots in the proof? will it hurt my score if i miss one step?
1. communication

# data[].attributes.body
I learned how to prove that certain lines were parallel or perpendicular, as well as how to find congruent angles. I still am wondering how  to do more advanced triangle and rectangular shapes, as those tend to be harder for me. Our group had good communication and was able to work together well.

# data[].attributes.body
1. How to determine other  angles
2. no questions
3. We worked together very well

# data[].attributes.headline
3. List givens first, some proof take more steps than others, and that sometimes it needs to be short and concise so it is easier to understand.

# data[].attributes.subject
3. List givens first, some proof take more steps than others, and that sometimes it needs to be short and concise so it is easier to understand.

# data[].attributes.body
2. NO questions I just need to have more practice
1. My team was really good at communicating and staying on task.

# data[].attributes.body
3 things I learned today were that make sure that you look at you're given
How to make sure there are enough proofs

We made sure and corrected mistakes fast and efficiently

# data[].attributes.body
1. My team was good at communicating and acting quickly as a team.

2. none

3.
a. slopes come in handy with proofs
b. knowing relationships between pieces of given information can be handy in a proof
c. knowing vocabulary for concepts is crucial in order for your proofs to be understood completely.

# data[].attributes.body
1.  the first statements should be givens
2. the last statement should be the prove statement
3. I learned new statements and rules that can be used to prove answers

1. how do you know which angles to use for a proof/which info?
2. what is the fewest statements that could be in a proof?

1.our group works together really well

# data[].attributes.body
3 Things I Learned:
1. There are many ways to write a proof.
2. You must write the givens first.
3. Don't add unnecessary information.
2 Questions I Still Have:
1. How do we know the best way to write a proof?
2. How do you type the congruent symbol?
1 Thing My Team Did Well Today:
1. We had very good equal conversations.

# data[].attributes.headline
3 things I learned were what a proof was, how to solve them, and the patterns they form when solving. 2 questions I have are - What is the difference between substitution and the transitive property? Do they have to always have a lot of detail/steps? 1. My group did a really good job of getting know each other today.

# data[].attributes.subject
3 things I learned were what a proof was, how to solve them, and the patterns they form when solving. 2 questions I have are - What is the difference between substitution and the transitive property? Do they have to always have a lot of detail/steps? 1. My group did a really good job of getting know each other today.

# data[].attributes.body
1. I learned what proofs are, how to solve them, and to write the given reasons first.
2. I don't have any questions at the moment.
3. We communicated well with each other

# data[].attributes.body
1. Three things I learned is that it is  important to write every steps with proofs, how to find evidence for proofs. and how to insert symbols on google.

2. I don't have any questions :)

3. We worked together to finish the assignment

# data[].attributes.body
3.
-Make sure to double check the given cause you can make silly mistakes yuh
-Uh- I kind of learned how to slove Proofs
- Learned to be able to connect proofs
2.
-How do proofs work  im dumb
-Why are proofs even useful?
1.
-We were able to easily communicate

# data[].attributes.body
1) i learned that the proofs should end with exactly the same as the prove at the top, no alternation

2)can proofs be abbreviations?

3) we talked and agreed

# data[].attributes.body
1. getting the work done.
2. How much proof do you really need?
3. How to prove how angles equal the same

# data[].attributes.body
1. I learned that you have to make sure you look at your givens, you have to make sure you're proving what they asked, and the difference between substitution and transitive property.
2. I don't have any questions
3. We work well at making sure we all agreed and talking.

# data[].attributes.body
3. I learned what a proof was, more vocabulary, and how to analyze problems closer
2. How do we get good at picking out certain parts of problems to use in our proofs? Is there ever more than one way to do a proof, or is there only one answer for each one?
3. I think my team was good at communicating.

# data[].attributes.body
3. things I learned during our proof activities are that the given statements are always first, there are multiple ways to prove a statement, and different vocab I can use to prove something
2. questions I have are... how do I come up with better statements? Will there always be given statements?
1. thing our group did well today is communication

# data[].attributes.body
3. things I learned were to double check your given, to double check you proved the right thing, and that finding lines parallel is important to proving angles congruent
2. questions I still have are none
1. thing our team did well was communicate

# data[].attributes.body
three things i learned are to end it with the answer, reasoning can be definitions, and follow patterns. Two things i wonder are the reasonings and the givens. my team communicated well

# data[].attributes.body
1)
- i learned what proofs actually are
- i wonder why proofs are useful
2)
- i learned more vocab
- what is a consecutive interior angle
3)
- i learned slopes are important
- can proofs b shortened

# data[].attributes.body
3. I learned about substitution, the transitive property, and names for rules that I already knew about.
2. Is there more than one way to describe the same rule?
Why do we need to use proofs?
1. We were discussing everything well.

# data[].attributes.body
I learned how to do proofs, learned what they are, and that givens should be stated first.
How do you know what to do first after the givens, thats the only question i have  :)
My team worked quickly and communicated ok

# data[].attributes.body
1. I learned that proofs actually have some use, vocabulary is necessary for proofs, and you have to know what lines are parallel first.
2.  No question's
3. My group is good at math

# data[].attributes.body
3 things I learned is that the proper symbols need to be used, transitive property and substitution are NOT the same thing, and that they can be done in different ways to reach the same result.
2 questions: Do proofs apply to things other than transversals? How will proofs help us in life in general? (that's the question kids ask for EVERYTHING in school isn't it...?)
1 thing my team did well was work speedily and efficiently together.

# data[].attributes.body
3 things I learned was how to analyze proofs more closely, more vocabulary, and that there are multiple ways to explain a problem.
2 How specific do we need to be? Why were proofs created?
1 thing our team did well was communicate

# data[].attributes.body
-1.  -double check your work
- write everything you know and then pick what to put into your proof

2.  what are proofs helpful for
is there more than one correct answer in a proof
how do you know what to put for the steps
3. something that my group did well was staying on topic

# data[].attributes.body
3. I learned that when you write that two angles are equal you do not put the congruent symbol, double check you wrote exactly what the given and proven say, substitution 2. how do you know if you wrote enough statements and is there a certain amount of steps you need. 1. one thing my team did well is listening to each other

# data[].attributes.body
1.)  I learned more vocabulary, I learned how to analyze proofs to see if they are correct, and I learned to double check to make sure what you are putting is actually true.
2.)can you have the same reasoning for your final proof and proofs above it, do you always have to do as many reasons as you can
3.) work together to find the mistakes

# data[].attributes.body
1. There's many ways to solve proofs, how to insert symbols, and what proofs are.
2. I don't have any questions.
3. We communicated well.

# data[].attributes.body
3 thing- Given statements come first, you do not always have to use all the boxes in the chart to complete a proof, and there are many ways to prove a proof statement.
Questions- What is the best way to go about starting a proof after the given/s?
Will we be spending more time on proofs?
Team- My team did really well communicating a deciding on one mutual decision for each statement and reason.

# data[].attributes.headline
1. One thing are group did well was communication.

# data[].attributes.subject
1. One thing are group did well was communication.

# data[].attributes.body
2. I wonder  how much proofs are used in the real world
I wonder why proofs were created.
3. I learned how to write proofs
i learned their are multiple ways to write proofs
I learned about how proofs the def of a proof

# data[].attributes.body
1. you do not need to many steps just enough to prove.
2.  Always put the given first
3. Always put the proof last.

1. When will we use proofs?
2. Are we going to see more proofs in other math classes?

1. Communicating

# data[].attributes.body
3 things that I learned during our proofs activity are multiple ways to prove that lines are parallel, that when comparing angle measures, use the equal sign instead of the congruent one, and what converses were.
2 questions I still have about proofs are what is substitution again and... yeah, that's it--
1 thing our team did well today in was all working together!

# data[].attributes.body
1.
1. I learned that the proofs can build on each other
2. I learned about the different properties and how they apply to proofs
3. I learned how to do a proof

2.
1. On the test will we have to write a whole proof or fill in the blanks?
2. When making your own proof do you need to write every step?

1.
1. One thing my group did well was communicate

# data[].attributes.body
1. I felt like we were able to communicate and come to agreements well.
2. I don't really have any questions.
3.
- Slopes can come in handy when writing/solving proofs.
- There is a difference between substitution and transitive property.
- When it's appropriate to use <1 and m<1.

# data[].attributes.body
1.  We communicated really well
2. no other questions
3. That Proofs don't need to be super long. You just need to prove what it's asking.

# data[].attributes.body
3. I have learned what a proof is and how to solve them; I learned about the Transitive Property; I learned that the givens always go first, the proof always goes last and they ahve to be word for word.
2. Are there more than one ways to solve proofs? On big tests like the ACT, do the answers always have to be written fully or can it be abreviated?
1. My team did really well at communicating and contributing to the problem.

# data[].attributes.body
Learned
1. vocab
2. definition of supp
3. congruence
Questions
1.I don't have any
Group did well
1. communicating

# data[].attributes.body
three things i have learned is using transitive property, how to find corresponding angles, and finding different equations. Two questions, sometime i just get confused on some of the meanings but that's all I have. Lastly we did good communicating our thoughts.

# data[].attributes.headline
3 finding parallel lines is important to getting solution

# data[].attributes.subject
3 finding parallel lines is important to getting solution

# data[].attributes.body
2 can you describe a rule more than one way
1 we worked fast and efficiently

# data[].attributes.body
3. I learned that each statement needs a reason. How to use converse. I learned that there are many ways to support your statement.
2. Do you always have to fill in the box?
1. We thought out the process and figured out what was needed and what wasn’t.

# data[].attributes.body
I learned in proofs when saying angles are equal you use the equal sign not congruent, it’s Important of 2 lines are parallel and I learned you don’t need to use a lot of steps,
I don’t have any questions
My team communicated well

# data[].attributes.body
1.  I learned you can be concise
I learned about substitution
I learned about the transitive property
2. What things should we focus on when starting the proofs?
I need help when it comes to the angles with letters (don't know how to phrase it as a question)
3. we were able to find the problems and solve them.

# data[].attributes.headline
3. I learned that there are multiple ways to solve proofs

# data[].attributes.subject
3. I learned that there are multiple ways to solve proofs

# data[].attributes.body
2.  I just need more practice
1. We got our work done on time.

# data[].attributes.body
1. communicate
2. no questions
3. proofs don't have to be long you just state what you see.

# data[].attributes.body
1. I learned that some things you do not need to be able to prove another thing, that proving something can be a long or short process, there are different ways to do it
2. I just need to keep practicing
3. We were very fast but we still talked about our answers

# data[].attributes.body
1. we all have talking and communicated together
2 I know how to write a successful prove.
3.I don't have question

# data[].attributes.body
1. Communicating and listening to each other

3. How to explain using less evidence

# data[].attributes.body
1. Three things I learned about proofs recently were how to apply the different converses, how to apply the transitive property to geometry, and that corresponding angles have to be on the same side of only one transversal.
2. Two questions I still have about proofs are: do you always need all the given information?, and what should you do when there are angles that are on the opposite side of a transversal but one is interior and one is exterior?
3. My group worked together to edit the proofs very well today.

# data[].attributes.body
1. given is always first
2. some proving can be more difficult and take longer than others
3. no questions

# data[].attributes.body
1. I learned more about transitive property and how to prove it, i learned how to prove a statement, and that you dont have to prove a reason
2.  Do you always have to use all the boxes, i only have one question
3. We worked really well together and talked a lot

# data[].attributes.body
1. Our group stayed on track
2. Why should we not abbreviate in reasoning? (Ex: Alt Ext Con)
3. There are soooo many ways to get to a proof.

# data[].attributes.body
3 things I learned about,  how to use correct terms, how to find the right symbols for proofs, and how to correctly write a proof
2. I don't have any questions.
1 one thing my teem did well today was communicating very well with each other.

# data[].attributes.body
3-
I learned how to ascertain what converse any given angle falls under
I learned how to compare congruent angles using the converses
I learned how to determine parallel lines using proof statements

2-
No questions

1-
We all had great teamwork, and worked perfectly to correct the proofs of our classmates.

# data[].attributes.body
1. a) you can do proofs different ways
b) there are many many relationships for proofs
c) the difference between transitive property and substitution
2. a) is it okay to do things differently
b) is it bad that i dont use as many lines as other people to explain if i still understand it
3. we did well working together and talking through the problem

# data[].attributes.body
1.  3 things learned;  the different symbols and what they mean/represent, how to use different methods to find the same answer, given is first.
2.  questions: do we have to use. every box on the chart to get the given answer?
3. we communicated and stayed on task

# data[].attributes.body
1. You always have to write down the given first, there is more than one way to prove something, and your last proof should always be your last proof.
2. Do you have to explain every specific step? ex: <2 is congruent to <4 because of alt, ext., but do you need to prove how the 2 lines are parallel if they aren't given? Another question; where should we start if we're having trouble starting somewhere?
3. We worked well together, everyone edited together.

# data[].attributes.body
3 things i learned were how to prove things on parallel lines, how to access special characters, and how proofs can make things easier
2 things i still question are how useful are proofs and how much will we use them
1 thing my team did well on was staying on task

# data[].attributes.body
1.  How to connect each thing to one another to form into evidence, how to explain using less evidence, proofs dont have to be as long as we make them to be 2. None 3. We communicated and worked quickly

# data[].attributes.headline
Rose Woodcock                        1. was stay on task and get work done quickly   

# data[].attributes.subject
Rose Woodcock                        1. was stay on task and get work done quickly   

# data[].attributes.body
2. not anything really specific but for me is writing all the specific steps down
3. examples in how to show al your steps

# data[].attributes.body
1.Three things that I learned today are;  you can prove many things on a line,  you have to  put the givens at the top of the list and the proves at the bottom,  people may prove things differently then you.
2. What is the difference between an angle relationship and converse?
3. My team did really well with getting the job done in our class.

# data[].attributes.body
3 things I learned was, the given goes first and the prove goes last. I learned the definition of transitive property. I learned new vocabulary.
2. Are there things we must include each time when stating a proof? How do you know if you included all proofs?
1 Our team asked questions when they didn't understand something.

# data[].attributes.body
What I learned:
1. Write the given first
2. Write the proof last
3. How to add math symbols
Questions:
1. Can the proofs be shown in more than one different way?
2. How do we know what to do after the given?
One thing we did well:
1. We agreed on everything

# data[].attributes.body
1.There are many different ways to do proofs
There isn't an exact amount of ways you can write proofs
All the different converses
2.No questions
3.The proof was a complete mess but my team communicated well to fix it