mirror of
https://github.com/btcsuite/btcd.git
synced 2024-11-19 01:40:07 +01:00
multi: fix typos
This commit is contained in:
parent
b4afc08a35
commit
019988b696
@ -137,7 +137,7 @@ type blockStore struct {
|
||||
// lruMutex protects concurrent access to the least recently used list
|
||||
// and lookup map.
|
||||
//
|
||||
// openBlocksLRU tracks how the open files are refenced by pushing the
|
||||
// openBlocksLRU tracks how the open files are referenced by pushing the
|
||||
// most recently used files to the front of the list thereby trickling
|
||||
// the least recently used files to end of the list. When a file needs
|
||||
// to be closed due to exceeding the max number of allowed open
|
||||
@ -224,7 +224,7 @@ func serializeBlockLoc(loc blockLocation) []byte {
|
||||
return serializedData[:]
|
||||
}
|
||||
|
||||
// blockFilePath return the file path for the provided block file number.
|
||||
// blockFilePath returns the file path for the provided block file number.
|
||||
func blockFilePath(dbPath string, fileNum uint32) string {
|
||||
fileName := fmt.Sprintf(blockFilenameTemplate, fileNum)
|
||||
return filepath.Join(dbPath, fileName)
|
||||
@ -780,7 +780,7 @@ func scanBlockFiles(dbPath string) (int, int, uint32, error) {
|
||||
// and offset set and all fields initialized.
|
||||
func newBlockStore(basePath string, network wire.BitcoinNet) (*blockStore, error) {
|
||||
// Look for the end of the latest block to file to determine what the
|
||||
// write cursor position is from the viewpoing of the block files on
|
||||
// write cursor position is from the viewpoint of the block files on
|
||||
// disk.
|
||||
_, fileNum, fileOff, err := scanBlockFiles(basePath)
|
||||
if err != nil {
|
||||
|
@ -223,8 +223,8 @@ commit messages.
|
||||
Here are some of the reasons why wrapping your commit messages to 72 columns is
|
||||
a good thing.
|
||||
|
||||
- git log doesn’t do any special special wrapping of the commit messages. With
|
||||
the default pager of less -S, this means your paragraphs flow far off the edge
|
||||
- git log doesn’t do any special wrapping of the commit messages. With the
|
||||
default pager of less -S, this means your paragraphs flow far off the edge
|
||||
of the screen, making them difficult to read. On an 80 column terminal, if we
|
||||
subtract 4 columns for the indent on the left and 4 more for symmetry on the
|
||||
right, we’re left with 72 columns.
|
||||
|
Loading…
Reference in New Issue
Block a user