Hi Docs group.Hi Chris

I have started to read the text below and I may I present some feedback. I have a slight rephrase of a sentenceBEFORE Some screens will be automatically configured depending on your hardware and the type of media you used to start the installation. You can still change the detected settings in any screen. Screens which have not been automatically configured, and therefore require your attention before you begin the installation, are marked by an exclamation mark. You can not start the actual installation process before you finish configuring these settings. AFTERSome screens will be automatically configured depending on your hardware and the type of media you used to start the installation. You can still change the detected settings in any screen. Screens which have not been automatically configured, are marked by an exclamation mark and therefore require your attention before you begin the installation. You can not start the actual installation process before you finish configuring these settings. CHANGE GO BACK to return If you incorporate the above change,  there is a "go back"  that could be replaced with "return" in the following The terminal multiplexer is running in virtual console 1. To switch from the actual installation environment to tmux, press Ctrl+Alt+F1. To go back to the main installation interface which runs in virtual console 6, press Ctrl+Alt+F6.

Software Selection My experience with anaconda is:If you select too many groups (eg all) to install, anaconda will definitely crash before completing the installation. Users should be cautioned to not install more than the necessary groups, and complete the installation of the remaining groups post installation  (sudo dnf group list).

From what I read below, it is very very well written and accolades to those who were the authors/editors

Regards  Leslie Leslie Satenstein Montréal Québec, Canada

On Sunday, August 23, 2020, 9:56:53 p.m. EDT, Chris Murphy lists@colorremedies.com wrote:

Hi,

This doc is in need of updating for the Btrfs by default feature approved for Fedora 33: https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Instal... https://fedoraproject.org/wiki/Changes/BtrfsByDefault

I can fork https://pagure.io/fedora-docs/install-guide and submit PR's. But I don't think that method is interactive, i.e. it's pretty much accept the PR or reject it, correct? Any other ideas?

I've identified these specific areas:

- Automatic partitioning -  should say Btrfs instead of LVM https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Instal...

- Some partition types - notably the /boot and /usr directories and the BIOS Boot and EFI partitions - can not be placed on Btrfs subvolumes. Use standard physical volumes for them (or an LVM logical volume for /usr). See Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended for more information.

- Ext4 is the default and recommended file system used by Fedora Workstation and Cloud.

- Advice on Partitions

- Recommended Partitioning Scheme (recommendations, sizes all need updates) https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Instal...

- Manual partitioning should say Btrfs instead of LVM https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/install/Instal...

- Silverblue https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/ https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-information...

- swap - based on your system parameters     - unrelated to btrfs, but needs updating for swaponzram feature https://fedoraproject.org/wiki/Changes/SwapOnZRAM

Original list and discussion appears here: https://pagure.io/fedora-workstation/issue/158#comment-672898

Thanks,

On Sun, Aug 23, 2020 at 07:55:45PM -0600, Chris Murphy wrote:

I can fork https://pagure.io/fedora-docs/install-guide and submit PR's. But I don't think that method is interactive, i.e. it's pretty much accept the PR or reject it, correct? Any other ideas?

Sorry, this is slow. But, no -- once create the PR, it can be commented on in review, and then any changes you push to the branch of your fork from which you created the PR (whew, that's a mouthful) will be automatically updated.