You do not need the plus in the square brackets, just the ones after the closing square bracket (is square bracket the right english word? - I'm talking about those:  ). Otherwise your code should be fine.
To prevent hostname canonicalization problems if your server is configured (now or later) with "UseCanonicalName On" and a non-canonical hostname is declared as the "ServerName," always specify the canonical hostname in any external redirect rule. That is: # Externally redirect to remove revision number and "/view" from the client-requested URL-path RewriteRule ^node/([0-9]+)/revisions/([0-9]+)/view$ http://www.example.com/node/$1? [R=301,L]
The most common manifestation of this problem is when the Webmaster has opted to use "www.example.com" and most or all inbound links point to that hostname, but ServerName is defined as "example.com" and UseCanonicalName is on. In cases like that, any request that triggers the rule will end up being redirected to the non-canonical hostname, and then perhaps get redirected again back to the canonical hostname (if you also have a rule to do that), resulting in stacked/chained/multiple redirects.
Search engines "don't like" chained redirects: They will be reported as errors in "Webmaster Tools" reports, and will not pass full ranking credit from old/incorrect URL links to the new/correct URL. And if no hostname canonicalization rule is in place, then the redirect to the non-canonical hostname effectively 'splits' your page-ranking credit, creates duplicate-content, and makes your site rely on the search engines' back-end de-duplication processes to 'clean up the mess."