Fix a broken link and build warning

[adiati98]

Description

This PR holds below changes:

• Fixed a broken link and addresses a build warning
• Applied vale off/on statements in config.rst.

Linked issue

Closes #267

Screenshots or screen recordings

[RCheesley]

Just one part where I think you need to shift the Vale off/on outside the PHP method/class declarations as the content isn't showing.

[RCheesley]

I don't think you can use Vale within the php class/method - this text seems to be missing:

Probs need to use it before the method declaration?

[adiati98]

I checked my changes, and it's the same with the live website. So they all actually broken.
Maybe let's just remove the vale here. Might give some errors, but it's because of the code

[adiati98]

This is weird. I removed the vale statements completely from here, but the result is still the same as your screenshot.

[adiati98]

I'm not familiar with php.
But can you confirm that the whole block is php code block?

.. php:class:: Mautic\CoreBundle\Event\RouteEvent

  .. php:method:: getType()

      :returns: The :ref:`route firewall<plugins/config:Routing firewalls>` for the given route collection.
      :returntype: string

  .. php:method:: getCollection()

      :returns: Returns a RouteCollection object that can be used to manually define custom routes.
      :returntype: \\Symfony\\Component\\Routing\\RouteCollection

  .. php:method:: addRoutes(string $path)

      Load custom routes through a resource file such as yaml or XML.

      :param string $path: Path to the resource file. For example, ``@FMElfinderBundle/Resources/config/routing.yaml``.
      :returntype: void

[adiati98]

If so, I think I know where it's gone wrong.

[adiati98]

I've removed the vale off/on. I'm not sure how these RST syntax should be rendered on the site, though. I'm asking confirmation from Rahul on Slack.

[adiati98]

The "rendering problem" has been fixed in #269. 👍🏼

[adiati98]

@RCheesley I've removed all vale statements. They don't seem to yell here.
The weird code rendered as you mentioned has been fixed in #269.

This PR now only holds below changes:

• Fixed a broken link that caused build fails.
• Removed excess empty lines.

So I think this is good to go.

[RCheesley]

GTG!

[RCheesley]

Does this also need fixing in other branches @adiati98 ?

[adiati98]

I think we only have one branch in developer docs?