---

yaml
---
r: 228971
b: refs/heads/try
c: 3f66928
h: refs/heads/master
i:
  228969: 1120dd0
  228967: ccefa71
v: v3

Author: Manishearth

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: aca2057ed5fb7af3f8905b2bc01f72fa001c35c8
 refs/heads/snap-stage3: 1af31d4974e33027a68126fa5a5a3c2c6491824f
-refs/heads/try: 8b60fe99ec7d52cf6de435d1414ea968105c11d4
+refs/heads/try: 3f6692874fdac72a7d0cbf578ed096ca8d0cbd1d
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/vec.md

@@ -442,7 +442,7 @@ end = ptr.offset(len)
 ```
 
 However because `offset` is marked as a GEP inbounds instruction, this will tell
-llVM that ptr is allocated and won't alias other allocated memory. This is fine
+LLVM that ptr is allocated and won't alias other allocated memory. This is fine
 for zero-sized types, as they can't alias anything. However if we're using
 heap::EMPTY as a sentinel for a non-allocation for a *non-zero-sized* type,
 this can cause undefined behaviour. Alas, we must therefore special case either