)]}'
{
  "commit": "06db47750e7de944b36a60d4028fbdf73e92cccc",
  "tree": "52230745080ccf1c83195a03a447963944cf1151",
  "parents": [
    "c8feb7c10b44d2a4ae2cf7a37bfda3e390a3f037"
  ],
  "author": {
    "name": "Adam Bender",
    "email": "abender@gmail.com",
    "time": "Sun Mar 09 22:12:14 2025 -0700"
  },
  "committer": {
    "name": "Gopher Robot",
    "email": "gobot@golang.org",
    "time": "Tue Mar 11 15:15:30 2025 -0700"
  },
  "message": "wiki: Prefer \"white space\" over \"whitespace\"\n\nBoth \"whitespace\" and \"white space\" are used in the codebase.\nThere doesn\u0027t seem to be an external consensus as to which is better\n(see https://github.com/orgs/mdn/discussions/382 for a discussion).\nhttps://www.unicode.org/versions/Unicode16.0.0/UnicodeStandard-16.0.pdf\n(warning: 12 MB file) consistently uses \"whitespace\", but the character\nproperty is \"White_Space\".\n\nRegardless of which, if any, term is deemed to be preferred, I\nbelieve the Go codebase should at least be consistent.\n\nThis change was prompted by browsing pkg.go.dev/strings and\nsearching for \"whitespace\", which found only strings.FieldsSeq,\nnot strings.Fields, which uses \"white space\".\n\nChange-Id: I0ad850831e4359a8c84afffa4ad86373e14133ca\nReviewed-on: https://go-review.googlesource.com/c/wiki/+/656315\nReviewed-by: Rob Pike \u003cr@golang.org\u003e\nReviewed-by: Ian Lance Taylor \u003ciant@golang.org\u003e\nAuto-Submit: Ian Lance Taylor \u003ciant@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2d1ea8a2a0df3dd00b08b0f1f0d9b62ac7aff5d4",
      "old_mode": 33188,
      "old_path": "Spelling.md",
      "new_id": "85a5048a2e5941127ff4b5338f18f44ac2b77b37",
      "new_mode": 33188,
      "new_path": "Spelling.md"
    }
  ]
}