Skip to content

Commit a8e16c4

Browse files
committed
Improve wording on the Django how-to guide.
1 parent 43a3a63 commit a8e16c4

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/how-to/django.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
# Django
1+
# Using with Django
22

3-
htpy works great with Django. This page contains information how you integrate htpy with Django.
3+
htpy works great with Django. This guide shows how htpy can be integrated with your Django project.
44

5-
## Returning a htpy response from a Django view
5+
## Return a htpy response from a view
66

77
htpy elements can be passed directly to `HttpResponse`:
88

@@ -14,7 +14,7 @@ def my_view(request):
1414
return HttpResponse(html[body[div["Hi Django!"]]])
1515
```
1616

17-
## Using htpy as part of an existing Django template
17+
## Use htpy as part of an existing Django template
1818

1919
htpy elements are marked as "safe" and can be injected directly into Django
2020
templates. This can be useful if you want to start using htpy gradually in an
@@ -106,7 +106,7 @@ def my_form_success_page() -> Renderable:
106106
)
107107
```
108108

109-
## Implement custom form widgets
109+
## Custom form widgets
110110

111111
You can implement a custom form widget directly with htpy.
112112

@@ -126,7 +126,7 @@ class ShoelaceInput(widgets.Widget):
126126
return str(sl_input(attrs, name=name, value=value))
127127
```
128128

129-
## Using htpy components directly from a template
129+
## Using htpy components from a template
130130

131131
htpy includes a custom template backend that makes it possible to use htpy
132132
instead of Django templates in places where a template name is required. This

0 commit comments

Comments
 (0)