Great post, Form! Nicely done with the pics and simple steps. I thought I might add a couple of thoughts to hopefully give additional clarification.

1. For anyone struggling to make the transition to thinking it terms of MRAD instead of inches, let's talk angular measurement for a minute. Mils (MRAD) sound weird and unfamiliar to most guys. It's really just an angular unit like degrees are, so let's call them degrees for this explanation. Most guys can picture a 15 degree or a 45 degree angle in their heads- it's a unit of measure that we're familiar with. Let's suppose you were throwing a baseball or football to a friend that is 50 yards away. You'd need to aim your throw up in the sky at perhaps a 35 degree angle in order to land the ball in your friend's hands. If your throw hits a little low, say at your friend's feet instead of at his chest level, you're not going to say to yourself, "okay, that hit 4 feet low, so at 50 yards 4 feet translates into 9.6 degrees, so I'd better aim my throw another 9.6 degrees higher, for a total angle of 44.6 degrees, in order to land the ball at chest level", you're just going to intuitively aim the throw at a little steeper angle, and it'll hit higher on your friend's body. Well this is similar to converting inches to MOA or MRAD when shooting. It's just a bunch of extra thinking and work to be converting back and forth between linear and angular units, when you could just think in terms of the angle. Unlike the baseball/football, you're not going to adjust your rifle intuitively (Kentucky windage), instead you're going to use an optical, angular ruler (reticle) to measure the adjustment angle needed, and instead of 9.6 degrees, it'll be 0.2 or 1.5 MRAD, or something similar.

There are 360 degrees in a circle. Now instead of picturing a circle that's flat on the ground like a compass, picture a circle that's standing vertical like a Ferris wheel. You can imagine that circle being marked with 360, 1-degree tick marks all around its circumference. Now instead of imagining 1-degree tick marks, imagine that the circle is divided into 6 slices (well 6.28 to be more exact), and the tick mark on each slice is called a 1-radian mark. Now picture each of those slices being divided up into 1000 pieces, and each of those little pieces is approximately a milliradian (MRAD for short). When you adjust 1 MRAD, you're adjusting the angle by one of those tiny slices. Now with that out of the way, let's go back to degrees. If you change the angle of your football throw by 1 degree, that's a 1 degree change whether your friend is standing 10 yards away or 50 yards away. Of course a 1 degree change will land the football only 1" higher at 10 yards, but would land the ball 5" higher at 50 yards. Now if you had an optical angular ruler and could watch the ball land low, you'd be able to measure the angle you need to adjust your throw by, and could try to throw 9.6 degrees higher (your arm doesn't have adjustable turrets on it, unfortunately). So whether your target it as 10 yards or 50, if you see a 1 degree correction is needed, it's 1 degree. If your target is at 10,000 yards and you see in your angular ruler that you need a 1 degree angle correction, that means you need 1 degree. Same with MRAD. If your reticle shows 1 MRAD correction needed, that's the same at 100 yards or 500. Of course that would translate into 3.6" at 100 yards and 18" at 500 yards, but we don't need or want to translate. Keep it in MRAD and keep life simple. One MRAD.

Now we often measure group size in MOA because of industry standard convention, but we could easily use MRAD for that too, except that nobody would know what we were talking about grin Aside from that, measuring target size, windage hold-off, shot correction, lead for a moving target, etc, are all measured/held using MRAD.

2. To the guys noticing that the elevation and windage correction factors are set to "1", this is something that needs to be verified if you're using your scope for shooting much beyond 500 yards. If your turret adjustments are 100% perfect, then the correction factor should be set to "1". If the actual adjustment is 0.99 mil per 1 mil (10 clicks) dialed instead of the advertised 1 mil per 10 clicks, then your correction factor should be set to 0.99. You'll need to verify whether your specific ballistic app uses the correction factor as the ratio of actual to advertised adjustments, or advertised to actual. With Ballistic:AE it's actual to advertised, so if you find that your turret adjusts 0.102 mil per click instead of the advertised 0.1 mil per click (1.02 mil actual adjustment for 1 dialed mil, if you dialed in 10 clicks), then the correction factor should be set to 1.02 (a ratio of 1.02 actual divided by 1.00 advertised). This can be measured and verified using a Tall Target test with an accurate rifle, as well as by setting up your scope in a fixture and testing tracking, or alternatively by measuring your reticle against a set subtension target at a set distance (to make sure your reticle is an accurate baseline), and then using an optical grid like the Bushnell magnetic boresighter to check that your turrets track properly as measured with your reticle. DON'T do this for your windage turret if you plan on using your reticle for windage holdoffs, that's assuming your reticle subtends true to form, as verified when doing the Tall Target test. Since we're using the reticle for windage, we don't care all that much what the turret does, and we want our ballistic app to spit out wind holds using the correct subtension of the reticle, not corrected for the actual adjustment increments of the windage turret. So if your reticle reads 5 MRAD, and that is truly 5 MRAD, leave the windage correction factor at "1".

This ensures that the ballistic app is telling you to adjust the ele. turret the correct amount, given how much each click is actually moving the reticle. At closer distances a 1 or 2% error isn't going to make a whole lot of difference in your shot solution (eg. 2.0 mil versus 2.04 mil), but can start to stack up when dialing in larger correction values.