DOC correct some typo in bug_triaging.rst (scikit-learn#19032)

doc/developers/bug_triaging.rst

@@ -1,7 +1,7 @@
 .. _bug_triaging:
 
 Bug triaging and issue curation
-================================
+===============================
 
 The `issue tracker <https://github.com/scikit-learn/scikit-learn/issues>`_
 is important to the communication in the project: it helps
@@ -10,7 +10,7 @@ priorities. For this reason, it is important to curate it, adding labels
 to issues and closing issues that are not necessary.
 
 Working on issues to improve them
---------------------------------------
+---------------------------------
 
 Improving issues increases their chances of being successfully resolved.
 Guidelines on submitting good issues can be found :ref:`here
@@ -36,22 +36,22 @@ The following actions are typically useful:
 
    Online discussions may be harder than it seems at first glance, in
    particular given that a person new to open-source may have a very
-   different understanding of the process than a seasonned maintainer.
+   different understanding of the process than a seasoned maintainer.
 
    Overall, it is useful to stay positive and assume good will. `The
    following article
    <http://gael-varoquaux.info/programming/technical-discussions-are-hard-a-few-tips.html>`_
    explores how to lead online discussions in the context of open source.
 
 Working on PRs to help review
-------------------------------
+-----------------------------
 
 Reviewing code is also encouraged. Contributors and users are welcome to
 participate to the review process following our :ref:`review guidelines
 <code_review>`.
 
 Triaging operations for members of the core and triage teams
--------------------------------------------------------------
+------------------------------------------------------------
 
 In addition to the above, members of the core team and the triage team
 can do the following important tasks:
@@ -91,7 +91,7 @@ See the github description for `roles in the organization
     should be closed.
 
 A typical workflow for triaging issues
-----------------------------------------
+--------------------------------------
 
 The following workflow [1]_ is a good way to approach issue triaging: