[Bug 826255] New: "home" points to the wrong page

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=826255

Bug ID: 826255
        QA Contact: [e-mail]
          Severity: unspecified
           Version: devel
          Priority: unspecified
                CC: [e-mail], [e-mail]
          Assignee: [e-mail]
           Summary: "home" points to the wrong page
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Unspecified
          Reporter: [e-mail]
              Type: Bug
     Documentation: ---
          Hardware: Unspecified
        Mount Type: ---
            Status: NEW
         Component: release-notes
           Product: Fedora Documentation

Description of problem:
on

http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Releas...

http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Releas...

http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Releas...

and

http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Releas...

, the "Home" button (at bottom of page) points to the same link as "Next",
instead of

http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html

Also, on the last two of the above pages, "Up" button points to the same link
as "Previous"

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

[Bug 826255] "home" points to the wrong page

[Red Hat Bugzilla]

Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=826255

Pete Travis  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |[e-mail]
         Resolution|---                         |CURRENTRELEASE
        Last Closed|                            |2013-02-10 14:32:24

--- Comment #1 from Pete Travis  ---
This issue appears to have been corrected in subsequent publishings of the
release notes. Thanks for reporting, cornel!