<commit_before>#Exercise 1:
![Screenshot 1](../../week-2/screenshot1.png)
#Exercise 2:
![Screenshot 2](../../week-2/screenshot2.png)
#Exercise 3:
![Screenshot 3](../../week-2/screenshot3.png)
#Exercise 4:
![Screenshot 4](../../week-2/screenshot4.png)
#Exercise 5:
![Screenshot 5](../../week-2/screenshot5.png)
#Exercise 6:
![Screenshot 6](../../week-2/screenshot6.png)
#Exercise 7:
![Screenshot 7](../../week-2/screenshot7.png)
#Exercise 8:
![Screenshot 8](../../week-2/screenshot8.png)
#Exercise 9:
![Screenshot 9](../../week-2/screenshot9.png)
#How can you use Chrome's DevTools inspector to help you format or position elements?
In the style section, once you've selected an element, you can set the display type and positioning type as well as chaning the margin, padding, top, bottom, left and right properties. When you change these properties

#How can you resize elements on the DOM using CSS?
You resize elements by changing the height and width of the element.

#What are the differences between Absolute, Fixed, Static, and Relative positioning? Which did you find easiest to use? Which was most difficult?
*With Absolute positioning, you can set the exact coordinates of the element relative to the ends of the screen
*With Relative positioning, you can set the coordinates of an element relative to where the element would normally lie.
*With Fixed positioning, you set the coordinates of the element the same way as Absolute, but it always stays in that position on the screen, no matter how much you scroll
*
Absolute positioning is the easiet to use I think b/c you don't have to worry about where the element would lie by default. You can set it exactly 

#What are the differences between Margin, Border, and Padding?
Margin is the space outside of the border. Border is the line (imaginary or displayed) enclosing the element. Padding is the space between the content of the element and the border.

#What was your impression of this challenge overall? (love, hate, and why?)
I thought it was easy most of the time. I enjoyed it because it gave us a chance to experiment with all of the positioning properties, which can be tricky.<commit_msg>fix markdown on chromedevtools reflection<commit_after>#Chrome Dev Tools

##Exercise 1:
![Screenshot 1](../../week-2/screenshot1.png)
##Exercise 2:
![Screenshot 2](../../week-2/screenshot2.png)
##Exercise 3:
![Screenshot 3](../../week-2/screenshot3.png)
##Exercise 4:
![Screenshot 4](../../week-2/screenshot4.png)
##Exercise 5:
![Screenshot 5](../../week-2/screenshot5.png)
##Exercise 6:
![Screenshot 6](../../week-2/screenshot6.png)
##Exercise 7:
![Screenshot 7](../../week-2/screenshot7.png)
##Exercise 8:
![Screenshot 8](../../week-2/screenshot8.png)
##Exercise 9:
![Screenshot 9](../../week-2/screenshot9.png)
##How can you use Chrome's DevTools inspector to help you format or position elements?
In the style section, once you've selected an element, you can set the display type and positioning type as well as chaning the margin, padding, top, bottom, left and right properties. When you change these properties

##How can you resize elements on the DOM using CSS?
You resize elements by changing the height and width of the element.

##What are the differences between Absolute, Fixed, Static, and Relative positioning? Which did you find easiest to use? Which was most difficult?
* With Absolute positioning, you can set the exact coordinates of the element relative to the ends of the screen
* With Relative positioning, you can set the coordinates of an element relative to where the element would normally lie.
* With Fixed positioning, you set the coordinates of the element the same way as Absolute, but it always stays in that position on the screen, no matter how much you scroll
* 
Absolute positioning is the easiet to use I think b/c you don't have to worry about where the element would lie by default. You can set it exactly 

##What are the differences between Margin, Border, and Padding?
Margin is the space outside of the border. Border is the line (imaginary or displayed) enclosing the element. Padding is the space between the content of the element and the border.

##What was your impression of this challenge overall? (love, hate, and why?)
I thought it was easy most of the time. I enjoyed it because it gave us a chance to experiment with all of the positioning properties, which can be tricky.
{'fraction_non_alphanumeric': 0.09455456823877877, 'fraction_numerical': 0.016404647983595352, 'mean_word_length': 4.334143377885784, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6980142', 'n_tokens_mistral': 1290, 'n_tokens_neox': 1185, 'n_words': 624}