Patch to resolve https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210360.
Details
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml | ||
---|---|---|
144 | This line changed in content, so whitespace changes here are allowed, but you can't bring stuff from the next unchanged line onto this one, because that changes whitespace on that line without changing content. | |
148 | Need to wrap the part starting with xlink to the next line. | |
150 | There is a space at the end of this line and the next. The rewording is good! | |
151 | There are trailing spaces on the next four lines. | |
154 | Use <acronym>RAM</acronym>. The "will" is not needed. There might be whitespace issues here, too. The rule is that whitespace can only be changed (like a sentence rewrap) if content on the same line changes. Otherwise, leave the lines ragged and plan on a second commit to fix whitespace. | |
165 | Put the most important stuff first, that being that this is the most common. Then say Intel uses a different name. There are invisible spaces at the end of these lines, too. | |
181 | Maybe "often" instead of "generally" (i386 is dying out), but not bad. Space at the end of this line also. | |
190 | Wording good, but can't rewrap the next line without introducing whitespace changes. | |
193 | There is an invisible space at the end of this line. | |
1674 | This is better, but it's kind of repetitive. Could remove that first part of the sentence, from "to ensure" to "to avoid". Probably better to say "erasing" or "overwriting" to avoid implying physical damage. |
en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml | ||
---|---|---|
154 | "specifications" is kind of odd. Maybe However, these small amounts of resources are | |
158 | "recommended to have" is roundabout. Let's make it simpler by splitting the sentence up: on usage. Some customized &os; systems use as little as 128 MB of <acronym>RAM</acronym>. General-purpose desktop systems need much more, and 2 GB to 4 GB is a good starting point. | |
160 | s/Here are/These are/ | |
169–170 | The word "type" helps here, s/processor/processor type/ | |
170 | To avoid redundancy, s/most modern/almost all common/ Be clear about what Intel does, and split the sentences: &intel calls it by a different name, <acronym>Intel64</acronym>. Other manufacturers sometimes call it <acronym>x86-64</acronym>.</para> Note the ending period. |
en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml | ||
---|---|---|
15 | "it is recommended to exceed" is kind of roundabout. How about combining this and the following two sentences: "However, such small amounts of memory and disk space are really only suitable for custom applications like embedded appliances." Then pick up with the "General-purpose..." | |
58 | s/disks/disk/ | |
61 | Is there a line or two missing here? |
Updating now, I went through the text line by line, and couldn't find any extra empty lines though.
Only one last note: the section on minimum RAM and disk space says that 2 to 4 G of RAM is a starting point, but does not mention disk space.
I'd say 8G is a reasonable minimum for desktop disk space. Or maybe we should say more?
- Fixed two whitespace errors.
- Reworded RAM recommendation and added hard drive space recommendation.
en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml | ||
---|---|---|
158 | "around" is kind of vague. "at least" is more definite. |