Bug 2225356 - The "Chapter 3. Updating Satellite Server, Capsule Server, and Content Hosts" within " Upgrading and Updating Red Hat Satellite" documentation should be renamed
Summary: The "Chapter 3. Updating Satellite Server, Capsule Server, and Content Hosts"...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 6.14.0
Assignee: Malhar Jivrajani
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-25 04:18 UTC by Jayant Bhatia
Modified: 2023-08-17 11:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-02 11:04:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19122 0 None None None 2023-07-25 04:20:04 UTC

Description Jayant Bhatia 2023-07-25 04:18:33 UTC
Document URL: 

https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/upgrading_and_updating_red_hat_satellite/index?lb_target=preview&check_logged_in=1#updating_satellite


Section Number and Name:

Chapter 4. Updating Satellite Server, Capsule Server, and Content Hosts
 

Describe the issue: 

The mentioned 'Chapter 4' does not contain any steps for updating Content Hosts. The Chapter name should be renamed from "Updating Satellite Server, Capsule Server, and Content Hosts" TO "Updating Satellite Server and Capsule Server".


Suggestions for improvement: As the Chapter does not contain any steps for updating content hosts, the Chapter name should be renamed to "Updating Satellite Server and Capsule Server".

Comment 1 Malhar Jivrajani 2023-08-02 07:30:02 UTC
Hi @jbhatia 

The work is already in-progress here: https://github.com/theforeman/foreman-documentation/pull/2233


Note You need to log in before you can comment on or make changes to this bug.