Bug 2218471 - [cee/sd][doc]Fix the typo in the section "Setting the initial CRUSH location of host"
Summary: [cee/sd][doc]Fix the typo in the section "Setting the initial CRUSH location ...
Keywords:
Status: RELEASE_PENDING
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.3
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 6.1z1
Assignee: Ranjini M N
QA Contact: Manisha Saini
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-29 09:33 UTC by Geo Jose
Modified: 2023-07-17 18:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-07 06:19:07 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6937 0 None None None 2023-06-29 09:33:49 UTC

Description Geo Jose 2023-06-29 09:33:19 UTC
Describe the issue:
------------------
 - Fix the typo in the section "Setting the initial CRUSH location of host" which is in operations guide

Describe the task you were trying to accomplish:
-----------------------------------------------
 - There is a typo in the section "Setting the initial CRUSH location of host" and which needs to be fixed.

Suggestions for improvement:
---------------------------
 - Modify as below(change "tp" --> "to"):
~~~
 You can add the location identifier to the host which instructs cephadm to create a new CRUSH host located in the specified hierarchy. 
~~~

Document URL:
------------
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html-single/operations_guide/index#setting-the-initial-crush-location-of-host_ops

Chapter/Section Number and Title:
---------------------------------
Chapter: 3
Section: 3.3. Setting the initial CRUSH location of host

Product Version:
----------------
RHCS 5.

Environment Details:
-------------------
NA

Any other versions of this document that also needs this update:
---------------------------------------------------------------
NA


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