Talk:.32 rimfire

This is the talk page for discussing improvements to the .32 rimfire article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Firearms Low‑importance

	This article is within the scope of WikiProject Firearms, a collaborative effort to improve the coverage of firearms on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.FirearmsWikipedia:WikiProject FirearmsTemplate:WikiProject FirearmsFirearms articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article has been marked as needing immediate attention.

United States Low‑importance

	United States portal This article is within the scope of WikiProject United States, a collaborative effort to improve the coverage of topics relating to the United States of America on Wikipedia. If you would like to participate, please visit the project page, where you can join the ongoing discussions. Template Usage Articles Requested! Become a Member Project Talk Alerts United StatesWikipedia:WikiProject United StatesTemplate:WikiProject United StatesUnited States articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article has been marked as needing immediate attention.

Article title

This page describes the .32 rimfire cartridge family, therefore should be in sentence case. StraightAsADie (talk) 03:19, 7 July 2013 (UTC)[reply]

History, .32 short or long

The .32 Short ?? was designed in 1860 by Smith & Wesson for their Model 2 revolver??. In 1868 they introduced the .32 Long in the Model 1½ Second Issue revolver ???. The S&W Model No. 2 made 1861-1874, was made for .32 long RF cartridges (Flayderman 8th Edition) -- hmaag (talk) 14:44, 31 October 2017 (UTC)[reply]