Skip to content

Commit eed5040

Browse files
committed
A couple of minor typos & clarification.
1 parent b8bffa9 commit eed5040

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

en/css/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Between the `<head>` and `</head>`, after the links to the Bootstrap CSS files a
100100
```html
101101
<link rel="stylesheet" href="{% static 'css/blog.css' %}">
102102
```
103-
The browser reads the files in the order they're given, so we need to be make sure this is in the right place. Otherwise the code in our file may override code in Bootstrap files.
103+
The browser reads the files in the order they're given, so we need to make sure this is in the right place. Otherwise the code in our file may override code in Bootstrap files.
104104
We just told our template where our CSS file is located.
105105

106106
Your file should now look like this:

en/django_models/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ class Post(models.Model):
123123
return self.title
124124
```
125125

126-
> Double-check that you use two undescore characters (`_`) on each side of `str`. This convention is used frequently in Python and sometimes we also call them "dunder" (short for "double-underscore").
126+
> Double-check that you use two underscore characters (`_`) on each side of `str`. This convention is used frequently in Python and sometimes we also call them "dunder" (short for "double-underscore").
127127
128128
It looks scary, right? But no worries we will explain what these lines mean!
129129

@@ -152,7 +152,7 @@ If something is still not clear about models, feel free to ask your coach! We kn
152152

153153
### Create tables for models in your database
154154

155-
The last step here is to add our new model to our database. First we have to make Django know that we have some changes in our model (we have just created it!). Type `python manage.py makemigrations blog`. It will look like this:
155+
The last step here is to add our new model to our database. First we have to make Django know that we have some changes in our model (we have just created it!). Go to your console window and type `python manage.py makemigrations blog`. It will look like this:
156156

157157
(myvenv) ~/djangogirls$ python manage.py makemigrations blog
158158
Migrations for 'blog':

0 commit comments

Comments
 (0)