Cleaned up some of the wording in the readme.

README.md

@@ -9,16 +9,17 @@ This library has been built for high quality data, with high quality footprints
 [See the wiki for installation information](https://github.com/issus/altium-library/wiki)
 
 # Need Access to Azure/Don't want to setup your own local MSSQL database?
-My development database is hosted on Microsoft Azure, and can be accessed from anywhere. Many organisations and universities are using the Azure database! Azure's firewall is fairly strict, and therefore requires me to explicitly allow you through. So please send your static IP address, Organisations IP Address range, or the IP range your dynamic IP address will be allocated from. Your IT Department or ISP can tell you this information. If you'd like read-only access to Azure, please send your IP address to markh@rris.com.au. I'm currently a bit behind in adding users, sorry.
+My development database is hosted on Microsoft Azure, and can be accessed from anywhere. Hundreds of organisations and universities are using the Azure database! Azure's firewall is fairly strict, and therefore requires me to explicitly allow you through. If you want to access the Azure database, please send your static IP address, Organisations IP Address range, or the IP range your dynamic IP address will be allocated from. Your IT Department or ISP can tell you this information. For read-only access to Azure, please send your IP address to markh@rris.com.au. I'm currently a bit behind in adding users, sorry.
 
-The Azure database is always up to date, the SQL dumps are typically thousands of components out of date as I am unable to push new files to GitHub LFS exept in the first day of my billing period if I can get in before the quota is used. If you wish to maintain a local copy of the database, it is most efficient to clone/sync from Azure. Visual Studio (even the free version) makes this very easy.
 
-Apologies to those who are trying to clone the SQL file from GitHub LFS - I do not have the funds to pay for increased bandwidth on my LFS account, so the LFS quota is typically used up within the first day of my billing cycle (as in, a day or two before my bill comes through). Its also therefore quite out of date as I cannot push updates to it very often.
+Apologies to those who are trying to clone the SQL file from GitHub LFS - I do not have the funds to pay for increased bandwidth on my LFS account, and the quote is typically used within the first hour or two of reset. Its also therefore quite out of date as I cannot push updates to it very often.
+
+If you wish to maintain a local copy of the database, it is most efficient to clone/sync from Azure. Visual Studio (even the free version) makes this very easy.
 
 
 # Why use an Altium DBLib over an Integrated Library?
 
-Altium Database libraries make you design your schematic with the part you are going to use, rather than a generic part with the same footprint. Rather than selecting "RJ45 Jack" you instead select Amphenol Commercial Products part number RJCSE538001. This is now reflected in your BOM completely, the entire BOM fills itself out, meaning no more trying to remember exactly what part you actually meant to put in there was, or what voltage that capacitor was.
+Altium Database libraries make you design your schematic with the part you are going to use, rather than a generic part with the same footprint. Rather than selecting "RJ45 Jack" you instead select Amphenol Commercial Products part number RJCSE538001. This is reflected in your BOM - the entire BOM fills itself out, meaning no more trying to remember exactly what part you actually meant to put in there was, or what voltage that capacitor was.
 
 Prior to using a DBLib, it would often take me half a day to fill out the bill of materials. I'd have to find each resistor on the supplier's website, list it down with the supplier's part number, manufacturer, manufacturer name, etc... Now I just generate the BOM in the output job, and everything is done. No more trying to remember "was that 33uF cap 25V or 50v?", or finding out after the fact that no, that capacitor isn't available as a 47uF 50V variant in that package, despite the fact you were sure it was!
 
@@ -31,26 +32,24 @@ Ultra librarian doesn't have high quality 3d models or parametrics. If all you n
 If you're integrating your electronic design into a housing or designing injection moulded cases for it - you need accurate 3d models or your mechanical engineers will spend a lot of time making sure the case fits your design files.
 
 ### Data
-All parts in the database are matched with every relevant parameter that Digi-Key carry for the part, so you can search/filter within Altium for the part you require. If you are looking for low Rds(on) N-Ch fets, just add the Rds(on) column to the Altium library window and sort by it.
+All parts in the database are matched with every relevant parameter that Digi-Key has for the part, so you can search/filter within Altium for the part you require. If you are looking for low Rds(on) N-Ch fets, just add the Rds(on) column to the Altium library window and sort by it.
 
 Every part has a link to the part on Digi-key, and has a link to the datasheet for the part for ease of design. Both the Digi-Key part number, price, and manufacturer name/part number are stored, now your BOM will be completely filled out automatically.
 
 ### Footprints
 Every part has a footprint created to match it's manufacturers recommended footprint by the manufacturer, or lacking that, an IPC Compliant footprint for the manufacturers specific package sizing. There are no generic footprints within this library, everything is manufacturer specific. 
 
-Every footprint must have a high quality, dimensionally accurate, accurately coloured 3d model. For complex parts (connectors like modular jacks), the manufacturers model is preferred however is always fully coloured and checked for accuracy against their drawings and modified as required.  I've found issues with the accuracy of the manufacturer issued model from most models, where they do not match the datasheet - every instance has been checked with the manufacturer and many have re-issued their 3d models because of these checks.
+Every footprint has a high quality, dimensionally accurate, accurately coloured 3d model. For complex parts (connectors like modular jacks), the manufacturers model is preferred however is always fully coloured and checked for accuracy against their drawings and modified as required.  I've found issues with the accuracy of the manufacturer issued model from most models, where they do not match the datasheet - every instance has been checked with the manufacturer and many have re-issued their 3d models because of these checks.
 
 Basic parts (TSSOP/SOP/Resistors etc) I have created every model from scratch in SolidWorks, if the manufacturers dimensions vary from the JEDEC standard, they receive their own version of the 3d model (see SOT-23-3..) For ultra basic parts with no features (QFN/DFN), a black basic Altium 3D extrusion is used of the correct size.
 
 Every part's centre position is where the Pick and place head should grab the part. For companies running their own Pick and Place machine, this is very convenient compared to centres at pin 1/centre of pads - your pick and place export list now has centres in the correct location.
 
-Every part has all it's surface mount footprints added, whether I use them or not. PDIP footprints do not exist, except for connectors. All passives are available in 0201, 0402, 0603, 0805 and 1206, sometimes also 1210 footprints at the least.
-
 ### Symbols 
 
 Every symbol in the library is somewhat standardised as to where pins are located, such as VCC in the top left, GND in the bottom left, user function pins on the right (controllable inputs/outputs). Standard protocols like SPI have the pins in the same order in every part - however manufacturer datasheet labeling is kept (DOUT rather than MISO for example) to make it easier to reference the datasheet. All components within a database category should have similar if not identical layouts/pin groupings where possible. This makes it much easier to switch out components.
 
-All passive components, such as resistors and capacitors all have the same size component span, keeping your schematics tidy.
+All passive components, such as resistors and capacitors all have the same size symbol lead span, keeping your schematics tidy.
 
 # What components are contained in the library?
 There are currently over 27000 parts in the library, this number sounds quite large but when you consider you need every value of resistor in 1%, 0.5%, 0.25%, 0.1% and 0.05%, in 0201, 0402, 0603, 0805 and 1206... you're now looking at over 5000 resistors.
@@ -149,20 +148,14 @@ There are currently parts from over 120 manufacturers in the database.
 ##### Currently on my ToDo list:
  - STM32F series (STM32F4, STM32F3, STM32F0)
  - Si Labs Gecko series
- - AVR-ATMEGA/XMEGA (ultra low priority)
- - Video Filters
- - Video Sync Separators
  - Current Sensors (more of)
  - Dual Row Headers
  - Larger Terminal Blocks (5/5.08mm pitch)
  - Capacitance to Digital Converters
  - More LPC series of M0/M3/M4 (LPC4337)
  - Opto-isolators
- - RF Filters
  - RF SoC (EZR32WG, CC2640, nRF5)
  - RGB LEDS
- 
-It will likely be months before I make a significant dent on this list, adding a single microcontroller with all of its package variants can take several hours. The good news is that the more footprints I add, the more I find a manufacturers footprint already exists in the database.
 
 # Contributing