Skip to content

Commit cccb3c5

Browse files
committed
docs: fix section title marks
1 parent 62b43b9 commit cccb3c5

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

user_guide_src/source/incoming/content_negotiation.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
*******************
1+
###################
22
Content Negotiation
3-
*******************
3+
###################
44

55
Content negotiation is a way to determine what type of content to return to the client based on what the client
66
can handle, and what the server can handle. This can be used to determine whether the client is wanting HTML or JSON
@@ -13,9 +13,9 @@ can handle this for you.
1313
:local:
1414
:depth: 2
1515

16-
=================
16+
*****************
1717
Loading the Class
18-
=================
18+
*****************
1919

2020
You can load an instance of the class manually through the Service class:
2121

@@ -32,9 +32,9 @@ method:
3232
When accessed this way, the first parameter is the type of content you're trying to find a match for, while the
3333
second is an array of supported values.
3434

35-
===========
35+
***********
3636
Negotiating
37-
===========
37+
***********
3838

3939
In this section, we will discuss the 4 types of content that can be negotiated and show how that would look using
4040
both of the methods described above to access the negotiator.

0 commit comments

Comments
 (0)